You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Franz Garsombke (JIRA)" <ji...@codehaus.org> on 2007/01/30 21:33:44 UTC

[jira] Created: (MWAR-91) Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.

Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.
---------------------------------------------------------------------------------------

                 Key: MWAR-91
                 URL: http://jira.codehaus.org/browse/MWAR-91
             Project: Maven 2.x War Plugin
          Issue Type: Bug
    Affects Versions: 2.0.2
         Environment: Mac OSX. Maven 2.0.4
            Reporter: Franz Garsombke


I have a dependency defined below:

    <dependency>
      <groupId>com.foo.ejb.server</groupId>
      <artifactId>slm-ejb-server</artifactId>
      <type>test-jar</type>
      <scope>compile</scope>
    </dependency>    	

I would expect it in the WEB-INF/lib directory at time of packaging. Interestingly enough its transitive dependencies show up but not the actual test jar. The reason we need it in the WAR is for Cactus tests. I agree Cactus is evil but can not remove it in the short term.

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

        

[jira] Closed: (MWAR-91) Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.

Posted by "Stephane Nicoll (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stephane Nicoll closed MWAR-91.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 2.0.3

applied, thanks!

> Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.
> ---------------------------------------------------------------------------------------
>
>                 Key: MWAR-91
>                 URL: http://jira.codehaus.org/browse/MWAR-91
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>         Environment: Mac OSX. Maven 2.0.4
>            Reporter: Franz Garsombke
>         Assigned To: Stephane Nicoll
>             Fix For: 2.0.3
>
>         Attachments: MWAR-91-maven-war-plugin.patch, MWAR-91-test.tar
>
>
> I have a dependency defined below:
>     <dependency>
>       <groupId>com.foo.ejb.server</groupId>
>       <artifactId>slm-ejb-server</artifactId>
>       <type>test-jar</type>
>       <scope>compile</scope>
>     </dependency>    	
> I would expect it in the WEB-INF/lib directory at time of packaging. Interestingly enough its transitive dependencies show up but not the actual test jar. The reason we need it in the WAR is for Cactus tests. I agree Cactus is evil but can not remove it in the short term.

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

        

[jira] Updated: (MWAR-91) Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.

Posted by "Piotr Tabor (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Tabor updated MWAR-91:
----------------------------

    Attachment: MWAR-91-test.tar

Simple project to reply the issue on 2.0.2 version, 
and not to reply the issue on patched 2.0.3 version

> Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.
> ---------------------------------------------------------------------------------------
>
>                 Key: MWAR-91
>                 URL: http://jira.codehaus.org/browse/MWAR-91
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>         Environment: Mac OSX. Maven 2.0.4
>            Reporter: Franz Garsombke
>         Attachments: MWAR-91-maven-war-plugin.patch, MWAR-91-test.tar
>
>
> I have a dependency defined below:
>     <dependency>
>       <groupId>com.foo.ejb.server</groupId>
>       <artifactId>slm-ejb-server</artifactId>
>       <type>test-jar</type>
>       <scope>compile</scope>
>     </dependency>    	
> I would expect it in the WEB-INF/lib directory at time of packaging. Interestingly enough its transitive dependencies show up but not the actual test jar. The reason we need it in the WAR is for Cactus tests. I agree Cactus is evil but can not remove it in the short term.

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

        

[jira] Updated: (MWAR-91) Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.

Posted by "Piotr Tabor (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MWAR-91?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Piotr Tabor updated MWAR-91:
----------------------------

    Attachment: MWAR-91-maven-war-plugin.patch

Patch to fix the issue (to revision 519283). 

> Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging.
> ---------------------------------------------------------------------------------------
>
>                 Key: MWAR-91
>                 URL: http://jira.codehaus.org/browse/MWAR-91
>             Project: Maven 2.x War Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0.2
>         Environment: Mac OSX. Maven 2.0.4
>            Reporter: Franz Garsombke
>         Attachments: MWAR-91-maven-war-plugin.patch
>
>
> I have a dependency defined below:
>     <dependency>
>       <groupId>com.foo.ejb.server</groupId>
>       <artifactId>slm-ejb-server</artifactId>
>       <type>test-jar</type>
>       <scope>compile</scope>
>     </dependency>    	
> I would expect it in the WEB-INF/lib directory at time of packaging. Interestingly enough its transitive dependencies show up but not the actual test jar. The reason we need it in the WAR is for Cactus tests. I agree Cactus is evil but can not remove it in the short term.

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