[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=346617#comment-346617
]
Martin Reinhardt commented on MECLIPSE-712:
---
this feature would be really helpful
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 was sent by Atlassian JIRA
(v6.1.6#6162)
[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=335924#comment-335924
]
Yariv Amar commented on MECLIPSE-712:
-
finx this can help with multi mpdule projects in eclipse. it would be great if
we the plugin supported this:
{code:XML}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
additionalConfig
filteredResources
filter
id1376227955734/id
name/name
type10/type
matcher
idorg.eclipse.ui.ide.multiFilter/id
arguments1.0-name-matches-false-false-*/arguments
/matcher
/filter
/filteredResources
/additionalConfig
/configuration
/plugin
{code}
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=335924#comment-335924
]
Yariv Amar edited comment on MECLIPSE-712 at 11/18/13 7:20 AM:
---
fixing this can help with multi module projects in eclipse. it would be great
if we the plugin supported this:
{code:XML}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
additionalConfig
filteredResources
filter
id1376227955734/id
name/name
type10/type
matcher
idorg.eclipse.ui.ide.multiFilter/id
arguments1.0-name-matches-false-false-*/arguments
/matcher
/filter
/filteredResources
/additionalConfig
/configuration
/plugin
{code}
this will make Eclipse ignore all the folders for sub-modules in the parent
project.
was (Author: yarix):
finx this can help with multi mpdule projects in eclipse. it would be great
if we the plugin supported this:
{code:XML}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.9/version
configuration
additionalConfig
filteredResources
filter
id1376227955734/id
name/name
type10/type
matcher
idorg.eclipse.ui.ide.multiFilter/id
arguments1.0-name-matches-false-false-*/arguments
/matcher
/filter
/filteredResources
/additionalConfig
/configuration
/plugin
{code}
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=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] (MECLIPSE-712) filteredResources in Eclipse .project is not supported and discarded by the Maven 2.x Eclipse Plugin
René de Bloois created MECLIPSE-712:
Summary: 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
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] (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:all-tabpanel
]
René de Bloois updated MECLIPSE-712:
-
Attachment: screenshot-1.jpg
This is how it looks in Eclipse.
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
