[
https://issues.jboss.org/browse/AS7-1236?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-1236.
-----------------------------------
Assignee: Brian Stansberry
Fix Version/s: 7.0.1.Final
Resolution: Done
Resolved via commit
http://github.com/jbossas/jboss-as/compare/664ec1d...4514477
Agreed that this is a mistake that people will make. So, the scanner now detects META-INF
and WEB-INF directories and will not recurse into them looking for deployments; instead an
ERROR is logged. This will prevent incorrect deployments being attempted in many, but not
all, cases and for cases where an incorrect deployment is attempted, the log message
hopefully will help the user to understand what went wrong.
Re: the .failed markers, yes, if the scanner finds something and tries to deploy it and
that fails, the .failed marker is the correct behavior.
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.1.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