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

Andreas Höhmann commented on MECLIPSE-273:
------------------------------------------

Here is another example of resources:

     <testResource>
        <directory>src/test/resources</directory>
        <filtering>true</filtering>
        <includes>
          <include>**/*.properties</include>
        </includes>
      </testResource>
      <testResource>
        <directory>src/test/resources</directory>
        <filtering>false</filtering>
        <includes>
          <include>**/*.xml</include>
          <include>**/*.DTD</include>
          <include>db/*</include>
        </includes>
      </testResource>

the eclipse-project only includes **/*.properties

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


Reply via email to