[jbosstools-issues] [JBoss JIRA] (JBIDE-10591) war module publishes exploded, ejb module is not
[
https://issues.jboss.org/browse/JBIDE-10591?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10591:
-----------------------------------------
Ah yes, that makes sense; m2eclipse of course synchronizes the Eclipse project with the
Maven pom configuration. I don't use EJB packaging type normally because I don't
use/need Eclipse JEE wizards (after all, EJB 3 tech basically turned it all into POJOs
with annotations) so I didn't even think about that.
I will make the change in the project I noticed the behavior first thing tomorrow morning,
I don't have direct access to it right now. I'm pretty sure that will correct the
behavior.
war module publishes exploded, ejb module is not
------------------------------------------------
Key: JBIDE-10591
URL: https://issues.jboss.org/browse/JBIDE-10591
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Reporter: erik van altena
Assignee: Fred Bricon
Priority: Minor
Fix For: 3.3.0.Beta1
Attachments: maven-testapp.zip
I have a simple mavenized project with a parent pom that manages an EJB, WAR and EAR
module, which I hot-deploy (or publish) to a JBoss 7 server by dragging the EAR module to
the server runtime. That part works.
However what I see is that the EAR and its child war module are deployed in exploded form
while the EJB module (also a child of the EAR) is deployed in its packaged jar form. That
means that the entire EJB module has to be published in stead of being able to hot-swap
code through an incremental publish. Unless I'm very badly mistaken of course.
"Deploy projects as compressed archives" is OFF by the way.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira