maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benjamin Leipold (JIRA)" <j...@codehaus.org>
Subject [jira] (MECLIPSE-704) Request to merge when 'filtering' is not identical
Date Sat, 18 Feb 2012 13:18:02 GMT

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

Benjamin Leipold commented on MECLIPSE-704:
-------------------------------------------

That's because the inferred result is wrong. Since eclipse does not support filtering, you
have to remove those entries and take a look at maven's result. All *.properties files should
be copied to the target directory. So, the correct inferred result should look like this:
{noformat}
<classpathentry kind="src" path="src/main/resources"/>
{noformat}
                
> Request to merge when 'filtering' is not identical
> --------------------------------------------------
>
>                 Key: MECLIPSE-704
>                 URL: https://jira.codehaus.org/browse/MECLIPSE-704
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>    Affects Versions: 2.7, 2.8
>            Reporter: Paul Mackinlay
>         Attachments: parent_pom.txt
>
>
> mvn eclipse:eclipse fails with a "Request to merge when 'filtering' is not identical"
message. There is a discussion about this on the internet and the accepted workaround is to
user eclipse plugin 2.6 (see http://forums.atlassian.com/thread.jspa?threadID=34952)
> In my case it is happening with non standard maven directory structure. The parent pom
has the config in the attached parent_pom.txt file.

--
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

        

Mime
View raw message