[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-1377) Deployed EAR project looses META-INF/application.xml
Juergen Zimmermann (JIRA)
jira-events at lists.jboss.org
Wed Nov 28 09:36:46 EST 2007
[ http://jira.jboss.com/jira/browse/JBIDE-1377?page=comments#action_12389620 ]
Juergen Zimmermann commented on JBIDE-1377:
-------------------------------------------
No I had the same error on my machine: same stack trace in the eclipse log, same records in the "Server view" event log.
One additional observation: Before the error happened I couldn't hot deploy as expected because the required J2EE module dependencies were partly lost. I selected the EAR project and added the lost "J2EE module dependencies" manually. Then I could select the EAR project to be deployed. However, during the hot deployment the error above happened.
> Deployed EAR project looses META-INF/application.xml
> ----------------------------------------------------
>
> Key: JBIDE-1377
> URL: http://jira.jboss.com/jira/browse/JBIDE-1377
> Project: JBoss Tools
> Issue Type: Bug
> Components: JBossAS
> Affects Versions: 2.0.0.CR1
> Environment: Eclipse 3.3.1.1, WTP 2.0.1, JBossTools, 2.0.0CR1
> Reporter: Juergen Zimmermann
> Fix For: 2.0.1
>
> Attachments: event-log.jpg
>
>
> After working a couple of days with JBoss Tools and doing hot deployment of the EAR project the deployment doesn't work any more. Both META-INF/application.xml and META-INF/jboss-app.xml aren't copied to the exploded ear directory any more.
> I tried
> a) eclipse -clean
> b) Disabling the JBoss Tools, restart Eclipse, (re-) enable JBoss Tools
> There is no success.
> The only solution was
> 1) Delete <workspace>/.metadata
> 2) Delete all subdirectories in eclipse/configuration so that only config.ini is there (as it was after unzipping eclipse)
> Hmm, same procedure in 3 days? Probabely yes, according to the same observation by my project collegues.
> I know about the vague description. However, I've no idea how to provide more information.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list