It came out shortly after beta9 when I discovered how broken putting extension entries in MANIFEST.MF was.

If it's killing you, you can delete the following from $MAVEN_HOME/plugins/maven-jar-plugin-1.0/plugin.jelly (or something like that)

Delete all of these lines from the jar creation section

<j:set var="extensionList" value=""/>
<j:forEach var="artifact" items="${pom.artifacts}">
<j:set var="dep" value="${artifact.dependency}"/>
<j:set var="extensionList" value="${extensionList},${dep.artifactId}"/>
</j:forEach>


<j:if test="${extensionList.length() != 0}"> <j:set var="extensionList" value="${extensionList.substring(1)}"/>
<ant:attribute name="Extension-List" value="${extensionList}"/>
</j:if>


<j:forEach var="artifact" items="${pom.artifacts}">
<j:set var="dep" value="${artifact.dependency}"/>
<ant:attribute name="${dep.artifactId}-Extension-Name" value="${dep.artifactId}"/>
<ant:attribute name="${dep.artifactId}-Implementation-Version" value="${dep.version}"/>
<ant:attribute name="${dep.artifactId}-Implementation-URL" value="http://www.ibiblio.org/maven${artifact.urlPath}"/>
</j:forEach>


Alex Vollmer wrote:

I've been running into JAR problems with weblogic's EJB Compiler when the extension information in the MANIFEST.MF file of a dependent JAR exists. The docs seem to indicate that you can turn this stuff off by setting the 'maven.jar.manifest.extensions.add' property to 'false'. However, looking through the Jelly code it doesn't look like this is used in beta-9 anywhere. Is this old documentation, or a feature that is in forward-development and not in beta-9?

Thanks!

--Alex




--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]





--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to