[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Jim Tyrrell commented on AS7-1236:
----------------------------------
Yeah I get that a jar file is a standard deployment, but it is usually in the context of a
war/ear/etc....just found it odd that something in a directory that did not end in the
well known types (war, ear, sar, etc) would be scanned, and then that it would be crawled
it, and .failed file would be created in the exploded directory..just odd to me.
Are there cases where other "things" could be done to an exploded directory?
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