[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-4655) Mavenized Project Examples and Seam Web Project wizard with JBoss Maven Integration facet don't work when using WTP 3.1 final

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-4655:
--------------------------------------

Sorry for the mistake. The problem isn't in WTP 3.1, but in JBoss Tools and m2eclipse. I think it was introduced by fixing JBDS-4507 (06/18/2009)

If you try the following test case:

- import test1.zip archive to the workspace using Import>Existing Projects in Workspace
you will get the test1 dynamic web project and the test1EAR ear project 
- create an EAR file (right-click test1EAR and Export>Java EE>EAR file
you will get an archive file with the following structure

test1EAR.ear
  - test1.war

The problem is deploying this application to the JBoss Tools server.
If you use JBDS 2.1.0 or some JBoss Tools<20090618, you will get the following structure:

test1EAR.ear
  - test1-0.0.1.war

If you use JBoss Tools (>20090618), you will get the following structure:

test1EAR.ear
  - test1.war

The problem is caused by the following line:
...
<wb-module deploy-name="test1-0.0.1">
...
in test1/.settings/org.eclipse.wst.common.component.xml

Because of the way JBoss Tools was working until 06/18/2009, the problem with m2eclipse wasn't reproducible. Now, it can be reproduced in the 
following way:

- import the test.zip archive using Import>Existing Projects in Workspace
you will get the test dynamic web project and the testEAR ear project 
- create an EAR file (right-click test1EAR and Export>Java EE>EAR file
you will get an archive file with the following structure

testEAR.ear
  - test.war

The application is invalid because application.xml contains the following:
<module>
    <web>
      <web-uri>test-0.0.1-SNAPSHOT.war</web-uri>
      <context-root>test</context-root>
    </web>
  </module>

and because test-0.0.1-SNAPSHOT.war module doesn't exist (the EAR file contains test.war).

If you deploy testEAR to some JBoss Tools server using JDBS 2.1.0, you will get the following structure:

testEAR.ear
  - test-0.0.1-SNAPSHOT.war
and the application will work correctly.

If you deploy testEAR with the latest JBoss Tools (>20090618), you will get:

testEAR.ear
  - test.war

It seems that JBIDE-4507 fixes inconsistencies between WTP and JBoss Tools related to the deployment. However, there is an inconsistency between JBDS 2.0.0/2.1.0 and the current JBoss Tools.

If we keep the current way of deploying EAR applications, the application.xml can be fixed. 

There is yet another problem in m2eclipse that can be reproduced as follows: 

- close the test project from the test.zip archive
- open the test project
- create an EAR file (or deploy on the JBoss Tools server using the JBoss Tools trunk)

You will get the following structure:

testEAR.ear
  - test-0.0.1-SNAPSHOT.war

- close the testEAR project
- open the testEAR project
- create an EAR file (or deploy on the JBoss Tools server using the JBoss Tools trunk)

You will get the following EAR file:

testEAR.ear
  - test.war

I could try to create a patch for m2eclipse, but need to know in what way we will solve the problem of inconsistency between JBDS 2.0.0/2.1.0 and the current JBoss Tools.

> Mavenized Project Examples and Seam Web Project wizard with JBoss Maven Integration facet don't work when using WTP 3.1 final
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-4655
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-4655
>             Project: JBoss Tools
>          Issue Type: Bug
>          Components: maven, project-examples, UpStream
>    Affects Versions: 3.1.0.M3
>            Reporter: Snjezana Peco
>            Assignee: Snjezana Peco
>             Fix For: 3.1.0.M3
>
>
> Deployment has been changed between WTP 3.1M7 and WTP 3.1.0.
> WTP 3.1.0 ignores 
> <wb-module deploy-name="xxxx">
> in .settings/org.eclipse.wst.common.component

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