[
https://jira.codehaus.org/browse/MWAR-247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MWAR-247.
-------------------------------
Resolution: Won't Fix
Please refer to
https://cwiki.apache.org/confluence/display/MAVEN/The+Great+JIRA+Cleanup+of+2014
if you're wondering why this issue was closed out.
> When using archiveClasses and adding the classpath to the manifest, your new
> project jar is not added to the classpath
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: MWAR-247
> URL: https://jira.codehaus.org/browse/MWAR-247
> Project: Maven 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 was sent by Atlassian JIRA
(v6.1.6#6162)
