[
https://issues.apache.org/jira/browse/MTOMCAT-161?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13811290#comment-13811290
]
Tim Astle commented on MTOMCAT-161:
-----------------------------------
That sounds similar to something I've observed after I submitted a patch for
MTOMCAT-215, but I had only addressed manifests. I hadn't gotten around to
looking at why duplicate class files were being added to the bundle. I'm not
sure if this the same thing as reported, but it sounds somewhat similar.
> Executable WAR: extraDependencies (JARs) should not be extracted but used
> directly
> ----------------------------------------------------------------------------------
>
> Key: MTOMCAT-161
> URL: https://issues.apache.org/jira/browse/MTOMCAT-161
> Project: Apache Tomcat Maven Plugin
> Issue Type: Improvement
> Components: tomcat6, tomcat7
> Affects Versions: 2.0-beta-1
> Environment: tomcat7, windows, maven3
> Reporter: Manuel Hartl
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.2
>
>
> When i create exec-war to create a a self-executable webapp, dependencies (at
> least extraDependencies) war extracted and added directly to the resulting
> JAR.
> the resulting jar contains a META-INF with lots of duplicate MANIFEST files,
> etc.
> this at least breaks signed JARs (e.g. JCE providers)
--
This message was sent by Atlassian JIRA
(v6.1#6144)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
