[
https://issues.jboss.org/browse/AS7-3148?page=com.atlassian.jira.plugin.s...
]
Brian Stansberry resolved AS7-3148.
-----------------------------------
Fix Version/s: No Release
Resolution: Rejected
Closing as the mechanisms for establishing relationships between deployments as described
at
https://docs.jboss.org/author/display/AS71/Class+Loading+in+AS7 take care of the
issue.
Allow dependency configuration for deployment scanner
-----------------------------------------------------
Key: AS7-3148
URL:
https://issues.jboss.org/browse/AS7-3148
Project: Application Server 7
Issue Type: Feature Request
Affects Versions: 7.1.0.CR1
Environment: AS7.1.0.Final-SNAPSHOT in standalone using standalone-ha.xml
Reporter: Brent Douglas
Fix For: No Release
Attachments: deployment-scanner.log
It would be really handy to be able to specify dependencies for the deployment scanner to
abide by. E.g. I have an application with the following structure:
{code}
A.ear
|-B.jar
\-C.war
D.war
{code}
If D has a dependency on B and they are deployed at the same time I'll get:
JBAS014775: New missing/unsatisfied dependencies:
service jboss.module.spec.service."deployment.A.ear".main (missing)
dependants: [service jboss.module.service."deployment.D.war".main, service
jboss.deployment.unit."D.war".POST_MODULE]
service jboss.module.spec.service."deployment.A.ear.B.jar".main (missing)
dependants: [service jboss.module.service."deployment.D.war".main, service
jboss.deployment.unit."D.war".POST_MODULE]
It would be great though if I could specify that I don't want to deploy D until A is
deployed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira