[
https://jira.jboss.org/jira/browse/JBIDE-5152?page=com.atlassian.jira.plu...
]
Rob Stryker resolved JBIDE-5152.
--------------------------------
Resolution: Duplicate Issue
Duplicate of: JBIDE-5121
I believe I fixed this yesterday so it may be in the nightly builds by now. =] But
seriously, good catch. It's really good to know people are actually using this
feature. For a while I wondered if it was even being used ;)
This code needs to be unit tested badly but I've been very busy working on some other
stuff =/
But thanks for the catch! =D
JBoss AS plugin deploys Project Artifacts with wrong extention
--------------------------------------------------------------
Key: JBIDE-5152
URL:
https://jira.jboss.org/jira/browse/JBIDE-5152
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Archives, JBossAS
Affects Versions: 3.1.0.M4
Environment: Linux
Eclipse 3.5.SR1
Java 6 update 16
JBossTools 3.1.0.M4
Reporter: Erick Menezes
Assignee: Rob Stryker
I have a XXX.ear file, created using Project Archive, it deploys as XXX.ear.jar/XXX.ear
file on the deployment folder. It adds this XXX.ear.jar on top of the ear's structure,
but the rest is just like I created.
This used to work on JBoss Tools 3.1.0.M2, I worked this around by just replacing the
JBossAS plugin from the M2 version with the M4 version and worked nicely.
Steps to reproduce: 1) Create a Java Project
2) Create a EAR file using the Project Archive plugin
3) Add the archive created to the JBoss instance to be
used
4) Start the JBoss, deploying the EAR
5) Open the deployment folder and see the EAR's wrong
extension
--
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