[ http://jira.codehaus.org/browse/MECLIPSE-139?page=comments#action_74497 ]
Jochen Kuhnle commented on MECLIPSE-139:
----------------------------------------
This last patch also adds parameter forcePomProjects (expression
${eclipse.forcepomprojects}, default false).
This parameter forces the creation of .project files for pom projects, even if
no other workspace location is specified.
This is useful when using a flat directory layout where pom projects have their
own directory and no subdirs, e.g:
project
+--rootproject/pom.xml
+--module1/pom.xml
+--module2/pom.xml
....
> Eclipse plugin cannot handle Java source files in resource directories
> ----------------------------------------------------------------------
>
> Key: MECLIPSE-139
> URL: http://jira.codehaus.org/browse/MECLIPSE-139
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Affects Versions: 2.3
> Reporter: Jochen Kuhnle
> Fix For: 2.3
>
> Attachments: MECLIPSE-139-java-resources.patch,
> MECLIPSE-139-java-resources.patch, MECLIPSE-139-java-resources.patch
>
>
> The eclipse plugin cannot handle Java source files in resource directories:
> The resulting Eclipse configuration compiles the Java files, so the target
> directory contains the class files, but not the java sources.
> This is often troublesome in unit tests or when you need to use code
> templates, because you often get compile errors in the Workbench. The
> attached plugin allows to handle this situation in the following ways:
> 1. Default behavior: Work just as the plugin did before
> 2. Exclude Java files from resource dirs
> 3. Use an Ant builder to copy Java sources
> As a sideeffect, the patch also extends the handling of custom builders:
> Instead of just specifying a name, you can also specify the triggers and
> arguments.
--
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
