[jboss-jira] [JBoss JIRA] (AS7-3148) Allow dependency configuration for deployment scanner

[Brian Stansberry (JIRA)]

    [ https://issues.jboss.org/browse/AS7-3148?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12663355#comment-12663355 ] 

Brian Stansberry commented on AS7-3148:
---------------------------------------

Hi Jye,

I suggest you start a thread in the jboss-as7-dev mail list or on the forums about this. Or, if you're certain you have a reproducible bug, open a separate AS7 JIRA for with "OSGi" selected in "Component/s" field. That will get the OSGi guys looking at it. Sounds like an issue with how the OSGi subsystem is handling deployments, so their expertise is needed.

It's not a "deployment-scanner" bug though. The deployment-scanner just monitors a filesystem dir and if changes are found creates management operations and invokes them against the AS7 management API. It's just a client to the management API same as a user using the CLI is or a user using the console is. It has no control over what the server does when handling the operations it sends (unless the operations are somehow broken, which is exceedingly unlikely since they basically amount to saying "deploy foo.jar".)
                
> 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