You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jim Sellers (JIRA)" <ji...@codehaus.org> on 2009/10/29 15:50:27 UTC
[jira] Closed: (MECLIPSE-615) WTP does not link war's to a jar
module if it also uses a test-jar
[ http://jira.codehaus.org/browse/MECLIPSE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jim Sellers closed MECLIPSE-615.
--------------------------------
Resolution: Not A Bug
Fix Version/s: 2.7
Oie.
This can be lined up to improper configuration by someone else and me not being able to catch it.
In the war, the improper config was along the lines of:
<dependency>
<groupId>com.example</groupId>
<artifactId>WhatWTPTroubleJar</artifactId>
<version>0.0.1-SNAPSHOT</version>
<classifier>tests</classifier>
<scope>test</scope>
</dependency>
- using a "classifier"
The proper config for a testing jar is:
<dependency>
<groupId>com.example</groupId>
<artifactId>WhatWTPTroubleJar</artifactId>
<version>0.0.1-SNAPSHOT</version>
<type>test-jar</type>
<scope>test</scope>
</dependency>
- using a "type" of test-jar
Sorry for the noise in jira / mailing list.
> WTP does not link war's to a jar module if it also uses a test-jar
> ------------------------------------------------------------------
>
> Key: MECLIPSE-615
> URL: http://jira.codehaus.org/browse/MECLIPSE-615
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: WTP support
> Affects Versions: 2.7
> Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 15:10:27-0400)
> Java version: 1.5.0_16
> Java home: C:\devtools\java\jdk1.5.0_16\jre
> Default locale: en_CA, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Reporter: Jim Sellers
> Fix For: 2.7
>
> Attachments: WhatWTPTrouble.zipx
>
>
> If a war file refers to a jar module in the same project AND a test-jar from that same project it will
> 1) not link to the actual project [1]
> 2) not deploy the packaged .jar file
> 3) put both the jar and the jar's dependencies in the manifest.mf for the war
> 4) it puts the jar's dependencies into the war
> The war project is now in an inconsistent state.
--
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