[jboss-jira] [JBoss JIRA] Resolved: (JBMICROCONT-161) jars in subdirs are not being deployed

[Scott M Stark (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBMICROCONT-161?page=all ]

Scott M Stark resolved JBMICROCONT-161.
---------------------------------------

    Fix Version/s:  JBossMC_2_0_0 Beta3
       Resolution: Done

> jars in subdirs are not being deployed
> --------------------------------------
>
>                 Key: JBMICROCONT-161
>                 URL: http://jira.jboss.com/jira/browse/JBMICROCONT-161
>             Project: JBoss MicroContainer
>          Issue Type: Bug
>          Components: Deployment
>    Affects Versions:  JBossMC_2_0_0 Beta3
>            Reporter: Scott M Stark
>         Assigned To: Scott M Stark
>             Fix For:  JBossMC_2_0_0 Beta3
>
>
> An ear like the following:
> [starksm at succubus testsuite]$ jar -tf output/lib/jbosstest-web.ear
> META-INF/
> META-INF/MANIFEST.MF
> META-INF/jboss-app.xml
> jbosstest-web-ejbs.jar
> jbosstest-web.war
> lib/
> lib/util.jar
> root-web.war
> wars/
> wars/notjbosstest-web.war
> websubdir/
> websubdir/relative.jar
> cts.jar
> scripts/
> scripts/security-config-service.xml
> scripts/security-config.xml
> META-INF/application.xml
> produces a structural parse that recognizes websubdir/relative.jar as a jar, but when this is translated into DeploymentContexts its not being picked up. It could be that the jbossas EARStructure should override this to be an immediate child ContextInfo of the ear, but first need to see why its not being picked up.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira