[
https://jira.jboss.org/jira/browse/JBIDE-4629?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-4629.
--------------------------------
Fix Version/s: 3.0.2.GA
Resolution: Done
An obvious hack / workaround has been added, but the use case of a utility project inside
an ear now listens to the deploy-path in the component.xml.
The hack works for this specific case only. The code base had diverged quite a bit.
Publishing an EAR project with "In Lib Dir" utility jar
results in wrong file structure
---------------------------------------------------------------------------------------
Key: JBIDE-4629
URL:
https://jira.jboss.org/jira/browse/JBIDE-4629
Project: JBoss Tools
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.0.0.GA, 3.0.1.GA, 3.1.0.M2
Environment: Eclipse 3.4 and Eclipse 3.5, Windows Vista
Reporter: Brett Prucha
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.0.2.GA, 3.1.0.M3
Attachments: workspace-test.zip
When publishing an EAR project to a JBoss server the "In Lib Dir" checkbox
under the Java EE Module Dependencies of the EAR projects properties is not being applied
for utility projects. The jar file created by the utility project is always placed in the
root of the EAR folder even if the "In Lib Dir" box is checked. Exporting the
EAR project to an EAR archive file results in a compressed archive that properly places
the utility jar in the EARs lib folder. Checking the "Deploy projects as compressed
archive" checkbox produces an EAR archive that improperly has the utility jar in the
root of the EAR as well.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira