[jira] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
[
https://jira.codehaus.org/browse/MECLIPSE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=332043#comment-332043
]
Nicolas Ternisien commented on MECLIPSE-712:
Any news on this?
Thanks!
filteredResources in Eclipse .project is not supported and discarded by the
Maven 2.x Eclipse Plugin
Key: MECLIPSE-712
URL: https://jira.codehaus.org/browse/MECLIPSE-712
Project: Maven Eclipse Plugin
Issue Type: Bug
Components: Core : .project
Affects Versions: 2.8
Environment: Maven 3, Windows 7, Eclipse Indigo Service Release 1
Reporter: René de Bloois
Attachments: screenshot-1.jpg
There is a beautiful way to let Eclipse ignore the target folder:
{code:xml|title=.project}
?xml version=1.0 encoding=UTF-8?
projectDescription
...
filteredResources
filter
id1328280594689/id
name/name
type10/type
matcher
idorg.eclipse.ui.ide.multiFilter/id
arguments1.0-projectRelativePath-matches-true-false-target/arguments
/matcher
/filter
/filteredResources
/projectDescription
{code}
Which in Eclipse means (in the Edit Resource Filter window): Exclude all,
Folders, not recursive, Project Relative Path matches target case
sensitive.
This will cause Eclipse to completely ignore this folder and its contents.
Problem is, after running mvn eclipse:eclipse, this section is removed from
the .project file.
It is also not possible to configure the maven eclipse plugin to add this
filteredResources section.
Maybe it could even be generated by default by the maven eclipse plugin?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
[
https://jira.codehaus.org/browse/MECLIPSE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=305951#comment-305951
]
Nicolas Ternisien commented on MECLIPSE-712:
I do agree it would be really useful! I actually don't see why everything
except test-classes and classes are not filtered out by default by Maven
Eclipse plugin (generating the proper filters automatically in .project file).
Could it be somehow possible to configure everything Eclipse allows to do in
.project file in the Eclipse Maven plugin (meaning: all tags), this way, we
would not constantly complain about a missing feature, the integration would be
really better.
filteredResources in Eclipse .project is not supported and discarded by the
Maven 2.x Eclipse Plugin
Key: MECLIPSE-712
URL: https://jira.codehaus.org/browse/MECLIPSE-712
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : .project
Affects Versions: 2.8
Environment: Maven 3, Windows 7, Eclipse Indigo Service Release 1
Reporter: René de Bloois
Attachments: screenshot-1.jpg
There is a beautiful way to let Eclipse ignore the target folder:
{code:xml|title=.project}
?xml version=1.0 encoding=UTF-8?
projectDescription
...
filteredResources
filter
id1328280594689/id
name/name
type10/type
matcher
idorg.eclipse.ui.ide.multiFilter/id
arguments1.0-projectRelativePath-matches-true-false-target/arguments
/matcher
/filter
/filteredResources
/projectDescription
{code}
Which in Eclipse means (in the Edit Resource Filter window): Exclude all,
Folders, not recursive, Project Relative Path matches target case
sensitive.
This will cause Eclipse to completely ignore this folder and its contents.
Problem is, after running mvn eclipse:eclipse, this section is removed from
the .project file.
It is also not possible to configure the maven eclipse plugin to add this
filteredResources section.
Maybe it could even be generated by default by the maven eclipse plugin?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MECLIPSE-449) Facet Generation generates duplicate entries - breaks RAD/RSA support
[ http://jira.codehaus.org/browse/MECLIPSE-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=241277#action_241277 ] Nicolas Ternisien commented on MECLIPSE-449: Bug reproduced here. Facet Generation generates duplicate entries - breaks RAD/RSA support - Key: MECLIPSE-449 URL: http://jira.codehaus.org/browse/MECLIPSE-449 Project: Maven 2.x Eclipse Plugin Issue Type: Bug Components: WTP support Affects Versions: 2.5.1 Environment: WinXP, IBM RSA V7.0.0.6 (Eclipse 3.2.2) Reporter: Chris Graham Fix For: 2.9 Attachments: MECLIPSE-449.patch, sample-error.zip, sample-noerror.zip Using V2.5.1 of the maven-eclipse-plugin, I have some issues in getting the generated artifacts being correct. Take this section of the POM: additionalProjectFacets jst.java5.0/jst.java jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ /faceted-project You'll see that the jst.java facet is in there twice. Removing the facet from the list: additionalProjectFacets jst.ejb2.1/jst.ejb com.ibm.websphere.extended.ejb6.1/com.ibm.websphere.extended.ejb /additionalProjectFacets Generates this: faceted-project fixed facet=jst.java/ fixed facet=jst.utility/ installed facet=jst.utility version=1.0/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ installed facet=jst.ejb version=2.1/ /faceted-project Which is a little more correct. I consider this a bug, as the facets (by their very definition) are unique and should not be repeated. Additionally, when compared to a RSA (V7) generated one, it is missing the standard XML header: ?xml version=1.0 encoding=UTF-8? Also, where does the jst.utility facet come from? It's inclusion is getting in the way of RSA recognising it as a true J2EE component project (the EJB Deployment descriptor tree element does not display in the Project Explorer view in the J2EE Perspective). This is the complete RSA generated one, for reference: ?xml version=1.0 encoding=UTF-8? faceted-project runtime name=WebSphere Application Server v6.1/ fixed facet=jst.ejb/ fixed facet=jst.java/ installed facet=jst.ejb version=2.1/ installed facet=jst.java version=5.0/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project (Which raises another question, how do we specify the runtime items and if something is fixed or not?) However, to get it to be correctly recognised, all we need is this: faceted-project fixed facet=jst.java/ installed facet=jst.java version=5.0/ installed facet=jst.ejb version=2.1/ installed facet=com.ibm.websphere.extended.ejb version=6.1/ /faceted-project -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
