[ 
https://jira.codehaus.org/browse/MECLIPSE-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=358262#comment-358262
 ] 

Alexandre Garnier edited comment on MECLIPSE-695 at 11/29/14 3:14 PM:
----------------------------------------------------------------------

The problem come from 
[r8366|https://fisheye.codehaus.org/changelog/plexus?cs=8366] for PLXCOMP-145.
Changing the instantiation strategy to {{instantiation-strategy="per-lookup"}} 
has for consequence to re-instance the {{FileResourceLoader}} each time and so 
forget the path of the parent project as search path.

The solution will be to explicitly add parent project as search path (patch 
coming soon).


was (Author: zigarn):
The problem come from 
[r8366|https://fisheye.codehaus.org/changelog/plexus?cs=8366] for PLXCOMP-145.
Changing the instantiation strategy to {{instantiation-strategy="per-lookup"}} 
as for consequence to re-instance the {{FileResourceLoader}} each time and so 
forget the path of the parent project as search path.

The solution will be to explicitly add parent project as search path (patch 
coming soon).

> Problem of path for additionalConfig with sub-modules
> -----------------------------------------------------
>
>                 Key: MECLIPSE-695
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-695
>             Project: Maven Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Workspace settings
>    Affects Versions: 2.8
>            Reporter: Alexandre Garnier
>         Attachments: MECLIPSE-695.zip
>
>
> When defining path to additionalConfig files in parent pom (relative to 
> pom.xml location), sub-modules did not find them.
> {code:language=xml}
> [...]
> <modules>
>   <module>module</module>
> </module>
> [...]
> <build>
>   <pluginManagement>
>     <plugins>
>       <plugin>
>         <groupId>org.apache.maven.plugins</groupId>
>         <artifactId>maven-eclipse-plugin</artifactId>
>         <additionalConfig>
>           <file>
>             <name>.settings/org.eclipse.core.resources.prefs</name>
>             <location>settings/org.eclipse.core.resources.prefs</location>
>           </file>
>         </additionalConfig>
>       </configuration>
>     </plugin>
>   </plugins>
> </pluginManagement>
> [...]
> {code}
> {code}
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-eclipse-plugin:2.8:eclipse (default-cli) on 
> project module: Unable to resolve resource location: 
> settings/org.eclipse.core.resources.prefs
> {code}
> It works fine in 2.7.



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

Reply via email to