[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-9024) seam-registration examle from wolf test repo is incorrectly deployed

[Fred Bricon (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon resolved JBIDE-9024.
--------------------------------

           Labels: m2eclipse upstream  (was: )
    Fix Version/s: 3.3.0.M2
       Resolution: Done


component.xml is missing because it's defined as a web resource in maven-war-plugin. The m2eclipse-wtp version used in 3.3.0M1 doesn't support web resource (filtering), but the latest version does (you can use use https://repository.sonatype.org/content/sites/forge-sites/m2eclipse-wtp/0.13.0/N/0.13.0.201105110807/ as your update site). 
I didn't deployed on EAP but checked the produced EAR on a deploy-only server. component.xml is correctly deployed.

However, the EAR deployed by m2e-wtp is slightly different from the one generated by CLI, even though that shouldn't prevent deployment : current m2eclipse-wtp uses the application.xml and jboss-app.xml generated by maven under target/m2e-wtp/ear-resources instead of the ones under src/main/resources (which should be under src/main/application BTW).
The generated application.xml has a different <display-name>. You should add <displayName>Seam Registration</displayName> to the maven-ear-plugin configuration.
Furthermore the generated jboss-app.xml uses jboss-app_4_0.dtd instead of jboss-app_4_2.dtd. The EAR pom;xml should be changed to use <jboss><version>4.2</version>...</jboss>.
Once you fix the pom, the files under src/main/resources become redundant and useless, they can be deleted.

> seam-registration examle from wolf test repo is incorrectly deployed 
> ---------------------------------------------------------------------
>
>                 Key: JBIDE-9024
>                 URL: https://issues.jboss.org/browse/JBIDE-9024
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven
>    Affects Versions: 3.3.0.M1
>         Environment: JBossTools 3.3.0 M1 on top of indigo 3.7 M6a, org.eclipse.m2e.core (0.13.0.201103291237), org.maven.ide.eclipse.wtp (0.13.0.201103231111)
>            Reporter: Libor Zoubek
>            Assignee: Fred Bricon
>              Labels: upstream, m2eclipse
>             Fix For: 3.3.0.M2
>
>         Attachments: webapp.zip
>
>
> I am testing wolf repository (maven repo of EAP 5.1). There are several example projects. These examples depend on maven artifacts shipped by wolf repo. There is a problem with example called webapp-seam-registration. This example can be built and deployed using maven CLI (mvn install jboss:deploy). But .. when I import it into JBoss Tools using 'Import existing maven project' and then deploy it on EAP 5.1 I get deployment errors. I was comparing the deoplyed EARs and found out, that the problem is, that component.xml (contained in registration-web project) is not deployed/added to archive. 
> When deploying using mvn jboss:deploy components.xml gets into registration-ear.ear/jboss-seam-registration.war/WEB-INF
> but  when deploying by JBossTools components.xml is missing there.
> I am not sure if it is a bug in tooling or bad configuraion in pom. I'll attach example project together with settings.xml for easy configuration.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira