[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4809: -------------------------------------- application.xml is created by m2eclipse 0.9.9.200911171109 Max, Will we create jboss-app.xml and datasource file ? -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4809: -------------------------------------- m2eclipse creates application.xml. JBoss Tools also creates it for the JBoss AS 4.2. I just wanted to create jboss-app.xml (if its creation is defined in maven-ear-plugin) that would make easier importing a lot of existing maven applications that create jboss-app.xml using maven-ear-plugin. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] Max Rydahl Andersen commented on JBIDE-4809: -------------------------------------------- Current idea/thinking: IFF Maven command line will ignore these files and use its own then this generation would just be to make WTP happy and they would effectively be temporary files for users to ignore. The files should only be generated if they don't exist already and if we generate new ones should contain a comment a long the lines of: "<!-- This file is generated by JBoss Tools to keep both m2eclipse and WTP happy. You should not need to edit or put this file into your source code control system. If you don't want this file generated automatically it can be disabled in Preferences. -->" And then have the matching preferences to control this. -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] asookazian commented on JBIDE-4809: ----------------------------------- I am experiencing a related issue using Eclipse 3.5.2.SR2 and m2eclipse 0.10.0. The mvn build (when I run 'mvn clean install') is using a "bad" application.xml presumably generated by m2eclipse when the EAR is constructed (i.e. both packaged and exploded EAR versions have the bad application.xml). The contents of the bad application.xml look like this: <module> <ejb>com.echo.cis.ejb.dao-1.5.1-SNAPSHOT.ejb</ejb> </module> <module> <ejb>com.echo.cis.editors-1.5.1-SNAPSHOT.ejb</ejb> </module> <module> <ejb>com.echo.cis.crud.dao-1.5.1-SNAPSHOT.ejb</ejb> </module> <module> <ejb>/com.echo.cis.ejb.dao-1.5.1-SNAPSHOT.jar</ejb> </module> <module> <ejb>/com.echo.cis.crud.dao-1.5.1-SNAPSHOT.jar</ejb> </module> Note the ".ejb" extensions on some of the ejb modules above. The files exist in the EAR with .jar extensions so JBoss AS throws following exception when I deploy the EAR: 09:46:55,671 ERROR [MainDeployer] Could not initialise deployment: file:/C:/java/jboss-4.2.2.GA/server/default/deploy/com.echo.cis.gui.ear-1.5.1-SNAPSHOT.ear/ org.jboss.deployment.DeploymentException: url file:/C:/java/jboss-4.2.2.GA/server/default/deploy/com.echo.cis.gui.ear-1.5.1-SNAPSHOT.ear/com.echo.cis.services.merchant-1.5.1-SNAPSHOT.ejb could not be opened, does it exist? When I delete the "bad" application.xml in foo/src/main/application/META-INF directory and run 'mvn clean install' again, the application.xml in the packaged or exploded EAR is correct (i.e. all ejb module now have .jar extensions, not .ejb). -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] Fred Bricon commented on JBIDE-4809: ------------------------------------ You should also make sure maven uses its own application.xml. In maven-ear-plugin configuration, set the following : <generateApplicationXml>true</generateApplicationXml> <earSourceExcludes>**/application.xml, **/jboss-app.xml</earSourceExcludes> -- 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

[ https://jira.jboss.org/jira/browse/JBIDE-4809?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-4809: -------------------------------------- I sent a patch, but it wasn't applied. See http://archive.jaxen.codehaus.org/lists/org.codehaus.m2eclipse.dev/msg/4B... -- 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

[ https://jira.jboss.org/browse/JBIDE-4809?page=com.atlassian.jira.plugin.s... ] Snjezana Peco resolved JBIDE-4809. ---------------------------------- Fix Version/s: 3.2.0.Beta2 (was: 3.1.2) Resolution: Done This issue is fixed in m2eclipse-wtp 0.12.x. You can install m2eclipse-core and m2eclipse-wtp using https://repository.sonatype.org/content/repositories/forge-sites/m2e/0.12... and https://repository.sonatype.org/content/repositories/forge-sites/m2eclips... update sites. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-4809?page=com.atlassian.jira.plugin... ] Fred Bricon commented on JBIDE-4809: ------------------------------------ If you change the maven-ear-plugin configuration in the pom.xml (http://maven.apache.org/plugins/maven-ear-plugin/usage.html), saving the file will refresh application.xml and jboss-app.xml. And FYI, this is stock m2eclipse-wtp behavior, no JBT involved. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira