[
http://jira.codehaus.org/browse/MECLIPSE-551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175624#action_175624
]
Ari Meyer commented on MECLIPSE-551:
------------------------------------
Similarly, this kills Wicket users who follow the standard practice of having
the corresponding HTML template file in the same dir as the Java source file.
(Yes, one could put HTML files in another directory structure, but that's not
the typical practice.) I've reverted to 2.5.1, which works fine, but please
release a fix soon!
Thanks,
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
