You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Arnaud Heritier (JIRA)" <ji...@codehaus.org> on 2007/11/02 02:17:14 UTC
[jira] Updated: (MECLIPSE-139) Eclipse plugin cannot handle Java
source files in resource directories
[ http://jira.codehaus.org/browse/MECLIPSE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MECLIPSE-139:
-------------------------------------
Fix Version/s: (was: 2.5)
> 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
> Assignee: Kenney Westerhof
> 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