[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-9496:
------------------------------------

The utility project is being identified as a "single root" project. There seems to be a bug in the single root handler (an efficient handler for specific cases) where it ignores references that are not child modules. 

Workaround is to make your project NOT single root. Steps to do that include:
  1) Adding a new folder to your project called "garbage" or some other irrelevant name
  2) Adding a folder mapping from "garbage" to "/" via the module assembly page.

At this point your project is no longer single root and this bug is worked around. 

> [regression] - Exported files don't honor the module assembly settings
> ----------------------------------------------------------------------
>
>                 Key: JBIDE-9496
>                 URL: https://issues.jboss.org/browse/JBIDE-9496
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.3.0.M3
>         Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
>            Reporter: Fred Bricon
>            Assignee: Rob Stryker
>              Labels: archive, deployment, sar
>             Fix For: 3.3.0.M3
>
>         Attachments: JBIDE_9496_projects.zip
>
>
> I'm investigating ways to implement SAR support for maven projects (JBIDE-9127). 
> So far I've been adding the Utility Facet to such projects, so they can be deployed in EARs. 
> A SAR project can embed dependencies in a lib folder, inside the archive. 
> A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691 
> Unfortunately, it seems a regression has crept in, because using the same projects attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of sarproject.sar, when earproject is deployed on (any) JBoss AS.
> In this use case, I have 2 sample maven-less projects :
> -sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The resulting  org.eclipse.wst.common.component contains :
> {noformat}
> <project-modules id="moduleCoreId" project-version="1.5.0">
>     <wb-module deploy-name="sarproject">
>         <wb-resource deploy-path="/" source-path="/src"/>
>         <dependent-module archiveName="junit.jar" deploy-path="/" handle="module:/classpath/var/JUNIT_HOME/junit.jar">
>             <dependency-type>uses</dependency-type>
>         </dependent-module>
>     </wb-module>
> </project-modules>
> {noformat}
> -earproject : needed so sarproject can be a Module project. I've manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed. Here is the end result :
> {noformat}
> <project-modules id="moduleCoreId" project-version="1.5.0">
>     <wb-module deploy-name="earproject">
>         <wb-resource deploy-path="/" source-path="/EarContent"/>
>         <dependent-module archiveName="sarproject.sar" deploy-path="/" handle="module:/resource/sarproject/sarproject">
>             <dependency-type>uses</dependency-type>
>         </dependent-module>
>     </wb-module>
> </project-modules>
> {noformat}

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira