The following comment has been added to this issue:
Author: Felipe Leme
Created: Fri, 15 Oct 2004 2:47 PM
Body:
Arnaud,
I was wondering if the update=true was there for some reason (as all other plugins
like jar, ear, rar and ejb didn't set it), now I got the answer :-)
Anyway, if that's the case, it's just a matter of adding a new property (something
like maven.war.update), which by default should be false (that would break backward
compatibility, but I think the expected behaviour is always to create a fresh archive).
-- Felipe
PS: again, I think it's important for the archive plugins (jar, war, ejb, ear, etc..)
to be consistent, so if we add this property here we should add it to the others as
well
---------------------------------------------------------------------
View this comment:
http://jira.codehaus.org/browse/MPWAR-33?page=comments#action_25440
---------------------------------------------------------------------
View the issue:
http://jira.codehaus.org/browse/MPWAR-33
Here is an overview of the issue:
---------------------------------------------------------------------
Key: MPWAR-33
Summary: Plugin generates multiple Class-Path entries in the manifest file
Type: Bug
Status: Closed
Priority: Major
Resolution: FIXED
Original Estimate: Unknown
Time Spent: Unknown
Remaining: Unknown
Project: maven-war-plugin
Fix Fors:
1.7
Versions:
1.6
Assignee: Felipe Leme
Reporter: Jöran Stark
Created: Wed, 22 Sep 2004 1:38 PM
Updated: Fri, 15 Oct 2004 2:47 PM
Description:
Hi,
Running war:war (maven-war-plugin-1.6) the first time generates a manifest file with a
single Class-Path entry (correctly including the
dependencies), but running war:war a second time (with no clean-up done) generates
multiple Class-Path entries.
This problem does not occure when building the EJB's (maven-ejb-plugin-1.4). When I
compared theese two I noticed that the war-plugin does an update while the ejb-plugin
does not. By removing the update attribute the war-plugin works fine, for me anyway ;-)
I have the same problem with 1.7-SNAPSHOT from CVS-HEAD.
Since my project includes other developers and users I would like to avoid making
(local) changes in the plugin. Currently the solution is to do a clean-up in the
pre-goal to war:war.
Cheers
Joran
[manifest after first run]
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Built-By: Joran
Name: foo.bar
Specification-Title: foo-web
Specification-Version: 1.0
Specification-Vendor: Apache Software Foundation
Implementation-Title: foo.bar
Implementation-Version: 1.0
Implementation-Vendor: Apache Software Foundation
[manifest after second run]
Manifest-Version: 1.0
Ant-Version: Apache Ant 1.5.3
Created-By: 1.4.2_05-b04 (Sun Microsystems Inc.)
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Class-Path: jakarta-oro-jena-2.0.jar icu4j.jar antlr.jar
Built-By: Joran
Name: foo.bar
Specification-Title: foo-web
Specification-Version: 1.0
Specification-Vendor: Apache Software Foundation
Implementation-Title: foo.bar
Implementation-Version: 1.0
Implementation-Vendor: Apache Software Foundation
[a snippet from project.xml]
<dependency>
<groupId>jena</groupId>
<artifactId>icu4j</artifactId>
<jar>icu4j.jar</jar>
<properties>
<war.manifest.classpath>true</war.manifest.classpath>
</properties>
</dependency>
---------------------------------------------------------------------
JIRA INFORMATION:
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
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
