[jira] Commented: (MECLIPSE-273) Several resource directories with different includes and eclipse

["Fredrik Wendt (JIRA)" <ji...@codehaus.org>]

    [ http://jira.codehaus.org/browse/MECLIPSE-273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=152303#action_152303 ] 

Fredrik Wendt commented on MECLIPSE-273:
----------------------------------------

I ran across a similar example where WTP was tricked by eclipse:eclipse but mvn package built working package artifacts (a war project):

{quote}
<resources>
  <resource>
    <directory>src/main/resources</directory>
    <filtering>true</filtering>
    <includes>
      <include>filterMe.properties</include>
    </includes>
  </resource>
  <resource>
    <directory>src/main/resources</directory>
    <filtering>false</filtering>
    <excludes>
      <exclude>filterMe.properties</exclude>
    </excludes>
  </resource>
</resources>
{quote}

This will generate {{<classpathentry ... including="filterMe.properties" excluding="**/*.java"/>}} which leads to Web Tools Project only exporting {{filterMe.properties}} and skipping other files. The war file created in {{mvn clean package}} on the other hand will properly include all files in src/main/resources.

> Several resource directories with different includes and eclipse
> ----------------------------------------------------------------
>
>                 Key: MECLIPSE-273
>                 URL: http://jira.codehaus.org/browse/MECLIPSE-273
>             Project: Maven 2.x Eclipse Plugin
>          Issue Type: Bug
>          Components: Core : Dependencies resolution and build path (.classpath)
>    Affects Versions: 2.3
>            Reporter: ol
>         Attachments: 113428_295.jpg
>
>
> I define the resources like this in my project :
> <resources>
>     <resource>
>         <directory>src/main/resources</directory>
>         <filtering>true</filtering>
>         <includes>
>             <include>p1.properties</include>
>         </includes>
>     </resource>
>     <resource>
>         <directory>src/main/resources</directory>
>         <filtering>false</filtering>
>         <includes>
>             <include>p2.properties</include>
>         </includes>
>     </resource>
> </resources>
> Then I execute the maven-eclipse-plugin to generate the .classpath and .project file.
> The result is not why I expected :
> - only the first resource definition is taken into account (see screenshot)
> > the file p2.properties is not copied by the eclipse build mechanism.
> Proposed solution:
> When we define 2 resource definition on the same 'directory', the 'maven-eclipse-plugin' should merge the includes and excludes elements.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira