[
http://jira.codehaus.org/browse/MECLIPSE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=177543#action_177543
]
Ari Meyer commented on MECLIPSE-551:
------------------------------------
Also, since this breaks builds/deployments for so many users, it might be
worthwhile to put up a warning on the main page:
http://maven.apache.org/plugins/maven-eclipse-plugin/index.html. I spent a lot
of time debugging what appeared to be bizarre errors from my code (should have
made this one change separately from my other changes, but...). Had I known
about this issue, I wouldn't have upgraded to 2.6.
Thanks again,
Ari
> [regression] Resources are excluded if resource dir equals source dir
> ---------------------------------------------------------------------
>
> Key: MECLIPSE-551
> URL: http://jira.codehaus.org/browse/MECLIPSE-551
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path
> (.classpath)
> Affects Versions: 2.6
> Reporter: Benjamin Bentmann
>
> {code:xml}
> <build>
> <resources>
> <resource>
> <directory>src/main/java</directory>
> <includes>
> <include>**/*.properties</include>
> </includes>
> </resource>
> </resources>
> </build>
> {code}
> For a non-standard project layout like sketched above where some resource
> files reside next to the source files (e.g. Messages.properties in Mercury),
> the change for MECLIPSE-443 causes these resources files to be excluded from
> the build path since they don't match the filter "**/*.java". This can for
> instance cause test failures in Eclipse due to resources missing on the class
> path.
> When source and resource directories equal, the includes/excludes need to be
> merged.
--
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
