[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Libor Zoubek updated JBIDE-9053: -------------------------------- Fix Version/s: (was: 3.3.0.M2) Affects Version/s: 3.2.1.CR1 (was: 3.3.0.M1) Environment: JBossTools 3.2.1 CR1 org.eclipse.m2e.core (0.12.1.20110112-1712), org.maven.ide.eclipse.wtp 0.11.1.20101108-1810 or 0.12.0.20110421-1500 (was: JBossTools 3.3.0 M1 on top of indigo 3.7 M6a, org.eclipse.m2e.core (0.13.0.201103291237), org.maven.ide.eclipse.wtp (0.13.0.201103231111)) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Libor Zoubek updated JBIDE-9053: -------------------------------- Description: I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that application.xml (contained in registration-ear project) does not contain <module><ejb>jboss-seam.jar</ejb></module> Deployment from CLI works fine ->application.xml has proper content was: I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that component.xml (contained in registration-web project) is not deployed/added to archive. When deploying using mvn jboss:deploy components.xml gets into registration-ear.ear/jboss-seam-registration.war/WEB-INF but when deploying by JBossTools components.xml is missing there. I am not sure if it is a bug in tooling or bad configuraion in pom. I'll attach example project together with settings.xml for easy configuration. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Libor Zoubek commented on JBIDE-9053: ------------------------------------- this issue is not reproducible on org.eclipse.m2e.core (0.13.0.201103291237), org.maven.ide.eclipse.wtp (0.13.0.201103231111) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-9053: -------------------------------------------- is this issue still relevant ? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Fred Bricon edited comment on JBIDE-9053 at 7/18/11 11:02 AM: -------------------------------------------------------------- I tested the project on Helios SR2 + JBT 3.2.1CR3 + m2e 1.0 + m2e-wtp 0.13 (both m2e features being installed with JBT 3.2.1CR3 \o/) and EAP 5.1. The deployed EAR has the same contents as a CLI generated .ear. However, the deployed app won't work out of the box, because the deployed EAR uses the project name (register-ear.ear), and not the expected finalName as defined in the pom (jboss-seam-registration.ear). This is both a m2e-wtp and WTP limitation. In order to deploy the app, there are 4 solutions : 1 - open the Server configuration, go to the Deployment tab and change the deployment location to jboss-seam-registration.ear 2 - refactor the artifactId of registration-ear to jboss-seam-registration 3 - Modify the examples : * registration-ear/pom.xml : change the finalName to <finalName>registration-ear</finalName> * registration-web/src/main/webapp/WEB-INF/component.xml : change pattern to <core:init jndi-pattern="registration-ear/#{ejbName}/local"/> 4 - Modify the examples : * registration-web/pom.xml : change the jndiName property to <jndiPattern>registration-ear/#{ejbName}/local</jndiPattern> * registration-web/pom.xml : enable the webResource filtering (currently commented), * registration-web/src/main/conf/component.xml : use <core:init jndi-pattern="${jndiPattern}"/> was (Author: fbricon): I tested the project on Helios SR2 + JBT 3.2.1CR3 + m2e 1.0 + m2e-wtp 0.13 (both m2e features being installed with JBT 3.2.1CR3 \o/) and EAP 5.1. The deployed EAR has the same contents as a CLI generated .ear. However, the deployed app won't work out of the box, because the deployed EAR use the project name (register-ear.ear), and not the expected finalName as defined in the pom (jboss-seam-registration.ear). This is both a m2e-wtp and WTP limitation. In order to deploy the app, there are 4 solutions : 1 - open the Server configuration, go to the Deployment tab and change the deployment location to jboss-seam-registration.ear 2 - refactor the artifactId of registration-ear to jboss-seam-registration 3 - Modify the examples : * registration-ear/pom.xml : change the finalName to <finalName>registration-ear</finalName> * registration-web/src/main/webapp/WEB-INF/component.xml : change pattern to <core:init jndi-pattern="registration-ear/#{ejbName}/local"/> 4 - Modify the examples : * registration-web/pom.xml : change the jndiName property to <jndiPattern>registration-ear/#{ejbName}/local</jndiPattern> * registration-web/pom.xml : enable the webResource filtering (currently commented), * registration-web/src/main/conf/component.xml : use <core:init jndi-pattern="${jndiPattern}"/> -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9053: --------------------------------------- Fix Version/s: (was: 3.2.1.CR3) -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen updated JBIDE-9053: --------------------------------------- Fix Version/s: 3.3.0.Beta1 (was: 3.3.0.M4) Assignee: Fred Bricon (was: Max Rydahl Andersen) -- 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

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Fred Bricon commented on JBIDE-9053: ------------------------------------ I documented the issue in http://community.jboss.org/wiki/MavenArchetypeCreationGuidelines -- 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

[ https://issues.jboss.org/browse/JBIDE-9053?page=com.atlassian.jira.plugin... ] Rastislav Wagner closed JBIDE-9053. ----------------------------------- -- 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