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

Karl Heinz Marbaise updated MECLIPSE-576:
-----------------------------------------
    Comment: was deleted

(was: That's really cool. I would be interested in seeing more graphs of 
different information you pull from these logs.
http://astuce-clashroyale.com
http://fifa16hacked.com)

> Merge resource dirs shall pass gracefully
> -----------------------------------------
>
>                 Key: MECLIPSE-576
>                 URL: https://issues.apache.org/jira/browse/MECLIPSE-576
>             Project: Maven Eclipse Plugin (RETIRED)
>          Issue Type: Bug
>          Components: Core : .project
>    Affects Versions: 2.7
>            Reporter: yclian
>            Assignee: fabrizio giustina
>         Attachments: DIFF.txt
>
>
> .project generation is failing for folks in our team that have updated to the 
> 2.7 release. It's due to {{EclipseSourceDir#merge()}} added in this version. 
> The reason why it is failing at our end because we use resource filtering on 
> resources appearing on the same path, i.e.
> {noformat}
> <resources>
>       <resource>
>               <directory>src/main/resources</directory>
>               <includes>
>                       <include>**/*</include>
>               </includes>
>       </resource>
>       <resource>
>               <directory>src/main/resources</directory>
>               <includes>
>                       <include>**/*.properties</include>
>               </includes>
>               <filtering>true</filtering>
>       </resource>
> </resources>
> {noformat}
> {noformat}
> [INFO] Request to merge when 'filtering' is not identical. Original=resource 
> src/main/resources: output=target/classes, include=[**/*], 
> exclude=[**/*.java], test=false, filtering=false, merging with=resource 
> src/main/resources: output=target/classes, include=[**/*.properties], 
> exclude=[**/*.java], test=false, filtering=true
> {noforrmat}
> I don't think fixing the POM to fit the plugin is a feasible solution. We 
> have Spring XML files and other documents that use ant style properties and 
> we don't wish Maven to perform filtering for us on them (see first 
> {{<resource>}} tag). It should just pass it like what it used to be in 
> previous versions.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to