[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
Fred Bricon (JIRA)
jira-events at lists.jboss.org
Wed Aug 10 03:30:30 EDT 2011
[ https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12619888#comment-12619888 ]
Fred Bricon commented on JBIDE-9496:
------------------------------------
Actually, I stumbled upon this bug using a maven project initially, which already maps 2 source folders to / :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sar-0.0.1-SNAPSHOT">
<wb-resource deploy-path="/" source-path="/src/main/java"/>
<wb-resource deploy-path="/" source-path="/src/main/resources"/>
<dependent-module deploy-path="/lib" handle="module:/classpath/var/M2_REPO/commons-lang/commons-lang/2.5/commons-lang-2.5.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
> [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
More information about the jbosstools-issues
mailing list