>From version 2.3 on, resources are not always copied to the EAR structure
-------------------------------------------------------------------------

                 Key: MEAR-82
                 URL: http://jira.codehaus.org/browse/MEAR-82
             Project: Maven 2.x Ear Plugin
          Issue Type: Bug
    Affects Versions: 2.3.1, 2.3
            Reporter: Emmanuel
         Attachments: dummyProject.zip

I had a EAR project that copied resources from a higher-level folder (see " ../ 
" below). It worked perfectly with maven-ear-plugin version 2.2
With versions 2.3 and 2.3.1, it seems to have stopped working that way. 
However, I see nowhere an indication on whether it is a new feature / 
impovement or a bug. Or is it that I'm not using it the right way? But if so, 
how do you explain the change of behaviour between versions 2.2 and 2.3 ?

Here above is a part of a Ear POM that shows the problem.
And attached is a complete simple project to help reproduce the problem.

<packaging>ear</packaging>
[...]
    <resources>
                <resource>
                        <directory>../myResources</directory>
                        <targetPath>targResources</targetPath>
                        <includes>
                                <include>*.properties</include>
                        </includes>
                </resource>
    </resources>
        <plugins>
                <plugin>
                        <artifactId>maven-ear-plugin</artifactId>
                        <!-- From Version 2.3 on, resources are no longer 
copied properly. Bug or evolution? -->
                        <!--version>2.3.1</version-->
                        <version>2.2</version>
                </plugin>
        </plugins>
[...]

Hope this helps make a better (world?) plugin.

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