[
https://jira.jboss.org/jira/browse/JBIDE-5952?page=com.atlassian.jira.plu...
]
Dmitry Malchikov commented on JBIDE-5952:
-----------------------------------------
Rob,
there is the instruction how to reproduce this issue:
1. Prepare your environment
1.1 Download eclipse 3.6 M5 at
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...
1.2 Install m2eclipse from
http://m2eclipse.sonatype.org/sites/m2e and m2eclipse extras
http://m2eclipse.sonatype.org/sites/m2e-extras
1.3 Install latest jboss tools (actually m2eclipse integration and JbossAS tools).
2. Import project
2.1. Download project attached to this jira issue
https://jira.jboss.org/jira/secure/attachment/12332598/example.zip
2.2. Extract archive to your workspace
2.3. Click file/import: maven/existing maven project
2.4. Browse unpacked project and select it
2.5. Select all, and finish
3. Add jboss server at servers tab in eclipse and set "use jboss deploy folder"
setting in server properties
4. Add project ear to be published on added jboss server
5. Right click on ear in servers tab and select full publish
6. Explore deploy location and navigate to ear.ear/lib folder
7. Check mvel2-2.0.10.jar now it contains another jar with the same name
ear dependency jar is wrapped by another jar
--------------------------------------------
Key: JBIDE-5952
URL:
https://jira.jboss.org/jira/browse/JBIDE-5952
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS, maven
Affects Versions: 3.1.0.CR2
Environment: windows 7 x64, 32-bit JRE, eclipse 3.6 M5 32bit for windows, WTP 3.2
M5, maven 2.2.1, JBossAS Tools 2.1.0.v201002252131N-H17-GA, JBoss Maven Integration
1.0.0.v201002252131N-H17-GA
Reporter: Dmitry Malchikov
Assignee: Snjezana Peco
Fix For: 3.1.1
Attachments: example.zip
Maven project has ear and ejb modules. Ear module depends on ejb module and includes it
in result ear file. When deploying ear some kind of ejb dependencies jars are wrapped into
another jar. Example of jars: jtds-1.2.2.jar, jibx-run-1.2.1.jar, mvel2-2.0.10.jar.
Don't know really why these jars are wrapped into jar package (for example
mvel2-2.0.10.jar contains another mvel2-2.0.10.jar package which contains correct jar
content) there are many jars that are deployed correctly.
--
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