[ https://jira.jboss.org/jira/browse/JBIDE-3456?page=com.atlassian.jira.plu... ] Dirk Pitt updated JBIDE-3456: ----------------------------- Attachment: burnout.zip -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt updated JBIDE-3456: ----------------------------- Description: My project is not generated from the seamgen or from JBoss Tools Seam Wizard. I created from Wesley Hayes maven archetype and installed necessary facets in eclipse configuration (Seam Facet and Seam Settings).. If I build it with maven and deploy it, everything works fine. But if I say in the web project in eclipse, debug on the server, I am getting the exception during deployment that application.xml is not there and it is not really there under \.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_AS_4.2.3_Server\deploy... My project configuration seems to be valid one because I am getting all the content assist information for the seam and project runs correctly if it deployed externally to JBoss... May be JBoss Tools and m2eclipse plugin are colliding but it is very hard for me to tell that.. I am attaching my sample project also so may be you can also reproduce it... May be one other tip, in maven ear plugin, I can configure the application.xml to be built in the runtime and would be copied to the target\EAR\META-INF directory during the build time (and application.xml there after the maven install). What I don't know does Seam/JBoss Tools look to the target directory to find the application.xml or it is trying to copy it from the source directories. If it tries to copy from sources directory ies, that is bad because as I said, this file is placed to the compile directory (target in my case / standart maven configuration). But in anycase I think it makes more sense to find this file from the compile/build directory... was: My project is not generated from the seamgen or from JBoss Tools Seam Wizard. I created from Wesley Hayes maven archetype and installed necessary facets in eclipse configuration (Seam Facet and Seam Settings).. If I build it with maven and deploy it, everything works fine. But if I say in the web project in eclipse, debug on the server, I am getting the exception during deployment that application.xml is not there and it is not really there under \.metadata\.plugins\org.jboss.ide.eclipse.as.core\JBoss_AS_4.2.3_Server\deploy... My project configuration seems to be valid one because I am getting all the content assist information for the seam and project runs correctly if it deployed externally to JBoss... May be JBoss Tools and m2eclipse plugin are colliding but it is very hard for me to tell that.. I am attaching my sample project also so may be you can also reproduce it... -- 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-3456?page=com.atlassian.jira.plu... ] Alexey Kazakov reassigned JBIDE-3456: ------------------------------------- Assignee: Rob Stryker There is not any specific things of Seam. It's a matter of maven/m2eclipse and wtp. Rob is there anything we can do when application.xml is generated by build? -- 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-3456?page=com.atlassian.jira.plu... ] Max Rydahl Andersen updated JBIDE-3456: --------------------------------------- Assignee: Snjezana Peco (was: Rob Stryker) Labels: maven (was: ) Snjezana - got any idea ? (I've started adding maven labels to maven/m2eclipse related issues so we can easier track those) -- 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-3456?page=com.atlassian.jira.plu... ] Snjezana Peco updated JBIDE-3456: --------------------------------- Attachment: burnout2.zip -- 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-3456?page=com.atlassian.jira.plu... ] Snjezana Peco commented on JBIDE-3456: -------------------------------------- You can configure maven not to generate application.xml (see the generateApplicationXml element within the maven-ear plugin). Re your second question, I haven't used tycho and haven't built m2eclipse. I check out m2eclipse and JBoss Tools svn and run PDE Runtime. -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3456: ---------------------------------- You are right off course that I can configure maven not the create the application.xml but it is more confortable naturally to have it on the run.... But as said, what it puzziling me, lets say I would have java classes, they would be compiled and picked from the build directory and WTP would not have any problem with that why it has problems to pick application.xml from the build directory... -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3456: ---------------------------------- I am sorry but couldn't get your point...the main responsiblity of a deploy process should get the build artifacts or not? and nearly all relevant things for deploment are already copied to build folder (at least with Maven) WTP's EAR module must collect the artifacts from build directory or not...If there are classes there, they would be collected... So if it can collect them from build folder, it is known to the EarModule.... When Maven build is complete the sructure would be +classes +----META/INF +------application.xml Don't get me wrong, I am grateful for the efforts of Snjezana and yours(and I can live with solution provided here), I am just try to understand what is the blocking factor there... I can guess that WTPs EAR Module tries to get application.xml only from resources folder but if it is implicitly also in target/classes/META-INF/application.xml there can be a chance to get it also... As I said I can run JBT und m2eclipse in PDE now, I would try to figure out a way. Thx for the tips -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3456: ---------------------------------- Hi Snjezana, i had followed your instructions but it crashing when I try to make maven - install from Run menu for the ear with the following exception....(I got th trunk version of the JBoss Tools and m2eclipse from SVN) Needless to say it is working perfectly when I try to build from the command line.. I know this is no JBoss Tools problem, may be WTP, I will report it to m2eclipse JIRA also but may be you experienced something similar also... I am attaching the state of the project after my import may be you can tell me what I am doing wrong... A very interesting point is, when I build from the command line (and application.xml created dynamically) I got this <module> <web> <web-uri>burnout-web-1.0-SNAPSHOT.war</web-uri> <context-root>burnout-web</context-root> </web> </module> but if I build from eclipse with run - maven - install, I got this <module> <web> <web-uri>classes</web-uri> <context-root>/burnout</context-root> </web> </module> this is astonishingly similar to exception 'Cannot copy a directory: C:\DEV\wss\runtimejbt_configuration\burnout-web\target\classes; Did you package/install org.lotr.agile.burnout:burnout-web:war:1.0-SNAPSHOT:compile?' Any ideas... Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot copy a directory: C:\DEV\wss\runtimejbt_configuration\burnout-web\target\classes; Did you package/install org.lotr.agile.burnout:burnout-web:war:1.0-SNAPSHOT:compile? at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot copy a directory: C:\DEV\wss\runtimejbt_configuration\burnout-web\target\classes; Did you package/install org.lotr.agile.burnout:burnout-web:war:1.0-SNAPSHOT:compile? at org.apache.maven.plugin.ear.EarMojo.execute(EarMojo.java:200) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) ... 16 more -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3456: ---------------------------------- A small side note, during this exception I disabled application.xml generation I only turned it on to be able to copy/paste web module part.... -- 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-3456?page=com.atlassian.jira.plu... ] Dirk Pitt commented on JBIDE-3456: ---------------------------------- JIRA entry in m2eclipse http://jira.codehaus.org/browse/MNGECLIPSE-1173 -- 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-3456?page=com.atlassian.jira.plu... ] Snjezana Peco resolved JBIDE-3456. ---------------------------------- Fix Version/s: 3.1.0.CR1 (was: LATER) Resolution: Out of Date m2eclipse 0.9.9.200911171109 creates application.xml correctly. mvn install (package, clean...) works correctly when the workspace resolution is included. -- 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