[
https://issues.jboss.org/browse/JBIDE-10591?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10591:
-----------------------------------------
Alright, here are the steps I took;
- changed packaging type to ejb
- added ejb plugin descriptor to force EJB 3.1 version (otherwise Maven defaults to EJB
2.1)
- maven -> update project configuration
- got into the trouble that both the EJB facet and the 'utility' facet were
selected for some reason, unchecked utility (ejb facet properly set to 3.1)
- had to update project configuration again to make Eclipse understand I unchecked the
utility facet :/
- full publish; EJB module was not deployed at all
- remove everything in deployments folder
- full publish again, this time the project deploys perfectly and fully exploded (OT: that
is something you shouldn't discuss in an airport)
So the packaging type (and of course the missing EJB facet as a result of the omission)
was indeed the key to my problem. As far as I'm concerned the issue can be closed -
nothing to fix here.
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