[
https://jira.jboss.org/jira/browse/JBDEPLOY-60?page=com.atlassian.jira.pl...
]
Scott M Stark closed JBDEPLOY-60.
---------------------------------
Resolution: Duplicate Issue
Did not see that JBDEPLOY-59 had already been created.
Add nestedWarManfiestClasspath option for processing of war manifest
classpaths
-------------------------------------------------------------------------------
Key: JBDEPLOY-60
URL:
https://jira.jboss.org/jira/browse/JBDEPLOY-60
Project: JBoss Deployers
Issue Type: Feature Request
Components: structure
Affects Versions: JBDEPLOY-2.0.0.Beta18
Reporter: Scott M Stark
Assignee: Adrian Brock
Fix For: JBDEPLOY-2.0.0.CR1
As discussed in the forum thread there is a regression in the default behavior of how the
classpath of wars with manifest classpaths that reference parent deployment jars behaves
in jbossas5.0.0.CR1 vs jbossas5.0.0.Beta4 and jbossas4.x. We need an option to ignore
manifest classpath references to parent deployment classpath entries.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira