Fix for MPWAR-21; Allow generation of the Class-Path manifest entry from dependencies like

the ejb and jar plugins.
Add test for new feature


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@114961 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
dion committed 2004-03-31 06:35:23 +00:00
1 parent 9eb7900b75
commit cd21b97aca
4 files changed
+21

No files matched your search

+6
View File
@@ -31,6 +31,7 @@
<assert:assertFileExists file="${warDir}/WEB-INF/lib/commons-logging-1.0.3.jar"/>
<!-- check for manifest contents -->
<!-- a) Make sure existing manifest gets merged -->
<j:set var="unzipDir" value="${maven.build.dir}/unzippedWar"/>
<mkdir dir="${unzipDir}"/>
<unzip src="${warFile}" dest="${unzipDir}"/>
@@ -39,5 +40,10 @@
<j:if test="${!found}">
<fail>Manifest not merged</fail>
</j:if>
<!-- b) Make sure Class-Path entry is created -->
<j:set var="found" value='${manifest.indexOf("Class-Path: commons-logging-1.0.3.jar") ge 0}'/>
<j:if test="${!found}">
<fail>Class-Path not generated</fail>
</j:if>
</goal>
</project>
+1
View File
@@ -78,6 +78,7 @@
<url>http://jakarta.apache.org/commons/logging.html</url>
<properties>
<war.bundle>true</war.bundle>
<war.manifest.classpath>true</war.manifest.classpath>
</properties>
</dependency>
</dependencies>