[ 
https://jira.codehaus.org/browse/MECLIPSE-596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Michael Osipov closed MECLIPSE-596.
-----------------------------------

    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.

> Equal additionalConfig file locations in several multi-project modules lead 
> to the same config file for all those projects
> --------------------------------------------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-596
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-596
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Multi-projects
>    Affects Versions: 2.7
>            Reporter: Marc Rohlfs
>            Priority: Minor
>
> If You define equal additional configuration file locations in several 
> modules of a multi-project setup, the plugin uses the same configuration file 
> (the first that occures in the reactor) for all those projects.
> In a multi-project setup we use the following configuration file location for 
> several modules ({{module-a}}, {{module-c}}, {{module-d}}, ...):
> {code:xml}
> <additionalConfig>
>   <file>
>     <name>.springBeans</name>
>     <location>src/eclipse/config/springBeans.xml</location>
>   </file>
> </additionalConfig>
> {code}
> When we execute {{mvn eclipse:eclipse}} on the parent module, the 
> configuration file of the first module in the reactor, where this location is 
> defined (let's say it's {{module-a}}), is also used for all the other 
> projects ({{module-c}}, {{module-d}}, ...) that define an equal config file 
> location.
> When we tried to solve the problem by using the {{basedir}} property,
> {code:xml}
> <additionalConfig>
>   <file>
>     <name>.springBeans</name>
>     <location>${basedir}/src/eclipse/config/springBeans.xml</location>
>   </file>
> </additionalConfig>
> {code}
> we ran into antoher problem (don't know if this might even be treated as a 
> separate issue):
> {noformat}
> org.apache.maven.plugin.MojoExecutionException: Unable to resolve resource 
> location: D:\projects\my-project\module-a/src/eclipse/config/springBeans.xml
>   at 
> org.apache.maven.plugin.eclipse.EclipsePlugin.writeAdditionalConfig(EclipsePlugin.java:1031)
>   at 
> org.apache.maven.plugin.eclipse.EclipsePlugin.writeConfiguration(EclipsePlugin.java:972)
> {noformat}



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Reply via email to