[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Okay I guess on the .failed markers, but I have to ask a question, so if we are deploying
just things likes .war, .ear, .sar, and a host of other well known extensions, why would
this even happen. In the past I thought there was a "deployable" list of
extensions JBoss AS/EAP would look at what changed requirement/need wise, or was this just
some oversight? Also curious does stuff like this end up in unit tests? How would I look
at those if they exist?
copied lib directory in the deployments directory results in
deployment
-----------------------------------------------------------------------
Key: AS7-1236
URL:
https://issues.jboss.org/browse/AS7-1236
Project: Application Server 7
Issue Type: Feature Request
Environment: JBoss AS 7 CR 1
Reporter: Jim Tyrrell
Assignee: Brian Stansberry
Fix For: 7.0.0.Final
Attachments: Sample.war
Having an existing zipped up war file, and then unzipping it in the deployment directory,
creates a lib directory that has a bunch of jar files in it. It appears that these jar
files in this lib directory are marked as .failed as they are tried to be deployed.
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira