[jbosstools-issues] [JBoss JIRA] (JBIDE-10591) war module publishes exploded, ejb module is not
Fred Bricon (Updated) (JIRA)
jira-events at lists.jboss.org
Thu Jan 5 10:50:09 EST 2012
[ https://issues.jboss.org/browse/JBIDE-10591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Fred Bricon updated JBIDE-10591:
--------------------------------
Component/s: JBossAS/Servers
I can't reproduce this issue. Creating a multi module project (parent, ear, war, ejb) from the Java EE Project wizard in [JBoss Central|http://docs.jboss.org/tools/whatsnew/central/central-news-1.0.0.M5.html] the EJB project is deployed as an exploded jar for both jboss-as-web-7.0.2.Final and jboss-as-7.1.0.Beta1b.
Can you attach your zipped projects here (remove any code and obfuscate any sensible data) so we can try to reproduce the problem?
> 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, maven
> Affects Versions: 3.3.0.M5
> Reporter: erik van altena
> Assignee: Fred Bricon
> Priority: Minor
>
> 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
More information about the jbosstools-issues
mailing list