[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3456) application.xml is missing in Seam project when debug on server option is selected for the web application

[Dirk Pitt (JIRA)]

    [ https://jira.jboss.org/jira/browse/JBIDE-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12449854#action_12449854 ] 

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

> application.xml is missing in Seam project when debug on server option is selected for the web application
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-3456
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3456
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: JBossAS
>    Affects Versions: 3.0.0.cr1
>         Environment: Ganyede 3.4.1 JEE Version, JDK 6, JBoss Tools Nightly 20/12/2008, m2eclipse plugin 30/11/2008
>            Reporter: Dirk Pitt
>            Assignee: Snjezana Peco
>             Fix For: LATER
>
>         Attachments: burnout.zip, burnout2.zip, configuration.txt
>
>
> 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...

-- 
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