[
https://jira.codehaus.org/browse/MECLIPSE-139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MECLIPSE-139.
-----------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
Assignee, if you think you can fix this bug anytime soon, please reopen and
proceed appropriately.
> Eclipse plugin cannot handle Java source files in resource directories
> ----------------------------------------------------------------------
>
> Key: MECLIPSE-139
> URL: https://jira.codehaus.org/browse/MECLIPSE-139
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
