You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "mike (JIRA)" <ji...@codehaus.org> on 2011/01/06 14:32:57 UTC
[jira] Created: (MWAR-247) When using archiveClasses and adding the
classpath to the manifest, your new project jar is not added to the
classpath
When using archiveClasses and adding the classpath to the manifest, your new project jar is not added to the classpath
----------------------------------------------------------------------------------------------------------------------
Key: MWAR-247
URL: http://jira.codehaus.org/browse/MWAR-247
Project: Maven 2.x WAR Plugin
Issue Type: Bug
Components: manifest
Affects Versions: 2.1.1
Reporter: mike
When using archiveClasses and adding the classpath to the manifest, your new project jar is not added to the classpath. The reason this is a issue is because we are overwriting one of the classes in one of our dependent jars and want our class to take precedent. Ideally we would like to see our jar show up as the first entry in the classpath list.
Here is our maven-war-plugin configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-war-plugin</artifactId>
<version>2.1.1</version>
<configuration>
<archiveClasses>true</archiveClasses>
<webResources>
<resource>
<filtering>true</filtering>
<directory>src/main/webapp/META-INF</directory>
<targetPath>META-INF</targetPath>
</resource>
</webResources>
<filteringDeploymentDescriptors>true</filteringDeploymentDescriptors>
<archive>
<manifest>
<addClasspath>true</addClasspath>
</manifest>
</archive>
</configuration>
</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