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

Romain Gossé updated MECLIPSE-725:
----------------------------------

    Attachment: testPluginBug.zip

h2. Test case

# Unzip, import both projects in a fresh new eclipse workspace.
# Run eclipse:eclipse and see the problem in the .settings files. (look for 
"WRONG")
# Run eclipse:clean eclipse:eclipse after having commented the section in the 
parent pom to have the expected behavior.
                
> multiple additionalConfig entries throughout pom hierarchy produces 
> incoherent result
> -------------------------------------------------------------------------------------
>
>                 Key: MECLIPSE-725
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-725
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Workspace settings
>    Affects Versions: 2.9
>         Environment: windows, maven 3.0.4, eclipse helios
>            Reporter: Romain Gossé
>         Attachments: build.log, testPluginBug.zip
>
>
> My project specifies 2 additional eclipse configuration files with the 
> content to be found with a <location> tag. Only one of those file's content 
> is ok after having run eclipse:eclipse, the other has the content of another 
> additional configuration file that is specified in the super-pom.
> ---
> My project is a war module with a parent. The parent references the company's 
> super-pom.
> Super-pom has the following:
> {code}
> <plugin>
>   <groupId>org.apache.maven.plugins</groupId>
>   <artifactId>maven-eclipse-plugin</artifactId>
>   <version>${version.maven-eclipse-plugin}</version>
>   <configuration>
>     <useProjectReferences>false</useProjectReferences>
>     <downloadSources>true</downloadSources>
>     <downloadJavadocs>false</downloadJavadocs>
>     <additionalConfig>
>         <file>
>         <name>.settings/org.eclipse.core.resources.prefs</name>
>         <content>
>     <![CDATA[   
> encoding/<project>=${project.build.sourceEncoding}${line.separator}eclipse.preferences.version=1${line.separator}
>     ]]>
>         </content>
>         </file>
>     </additionalConfig>
>   </configuration>
> </plugin>
> {code}
> My projet has the following:
> {code}
> <plugin>
>                               <artifactId>maven-eclipse-plugin</artifactId>
>                               <configuration>
>                                       <wtpversion>2.0</wtpversion>
>                                       <additionalConfig>
>                                               <file>
>                                                       
> <name>.settings/org.eclipse.jdt.ui.prefs</name>
>                                                        
> <location>src/main/eclipse/ui_prefs.txt</location>
>                                               </file>
>                                               <file>
>                                                       
> <name>.settings/org.eclipse.jdt.core.prefs</name>
>                                                       
> <location>src/main/eclipse/core_prefs.txt</location>
>                                               </file>
>                                       </additionalConfig>
> {code}
> What expecting to get in the .settings folder is:
> * a file org.eclipse.jdt.ui.prefs containing what is in 
> src/main/eclipse/ui_prefs.txt
> * a file org.eclipse.jdt.ui.prefs containing whit is in 
> src/main/eclipse/core_prefs.txt
> What I got is:
> * (/) a file org.eclipse.jdt.ui.prefs containing what is in 
> src/main/eclipse/ui_prefs.txt
> * (x) a file org.eclipse.jdt.core.prefs containing the *same content as 
> org.eclipse.core.resources.prefs*
> If I switch the nodes' order in the <additionalConfig> tag, the problem will 
> still show up with the second entry.
> I will try to provide a full project hierarchy as a demonstration.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to