[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3874) Maven integration

[Snjezana Peco (JIRA)]

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

Snjezana Peco commented on JBIDE-3874:
--------------------------------------

>> The project can be run from the command line using maven 2.0.9 (probably 2.0.10),
>> but can't using Run As>Maven clean/Run As>Maven install.
>> The problem is that m2eclipse uses maven 2.1 that is not compatible with maven 2.0

> If that is actually the case, then you found incompatibility in Maven 2.1/3.0, so please report it to the Maven and/or m2eclipse JIRA.
> However, it could be also an issue with the pom.xml you generated. For example you should always specify versions of plugins you are using, especially the maven-war-plugin.

Adding versions to the maven plugins doesn't help. I have tried to add them to all the plugins we are using (war, ear, ejb, compiler and surefire).

> Also, it is misleading to say that "Run As>Maven ..." don't work, as compared to Maven 2.0.9 from the command line. Because that shortcut can be configured to use any version of Maven you want, including 2.0.9 

mvn clean install works from the command line when using maven 2.0.9 and 2.1.0. Run As>Maven clean/install doesn't work when using Embedded or External 2.0.9/2.1.0 maven installations. 
There is a bug in m2eclipse http://jira.codehaus.org/browse/MNGECLIPSE-1173 and in JBoss Tools https://jira.jboss.org/jira/browse/JBIDE-3456 related to this issue.

> Please report all bugs you found to m2eclipse JIRA. Though your description is somewhat confusing, so it would be really helpful if you provide a reproducible test case. 

- import the JBoss Tools Seam Booking Example - EAR mavenized 2.1.1.GA
- call Maven>Update Project Configuration

if your workspace is, for example, C:\workspace, m2eclipse will create the workspace/booking/WebContent directory and add the "<wb-resource deploy-path="/" source-path="/workspace/booking/WebContent"/>" entry to the org.eclipse.wst.common.component file. 
There are some more issues with this action. It tries to remove (and add) the Web Module facet which is not allowed by WTP. m2eclipse tries to avoid this constraint which is not possible if there are other facets ((JSF, Seam...) that depend on the Web Module facet .



> Maven integration
> -----------------
>
>                 Key: JBIDE-3874
>                 URL: https://jira.jboss.org/jira/browse/JBIDE-3874
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: common
>    Affects Versions: 3.0.0.GA
>            Reporter: Max Rydahl Andersen
>            Assignee: Snjezana Peco
>            Priority: Critical
>             Fix For: 3.1.0.M2
>
>
> It is time to make sure our stuff works well with Maven, at least to the extent that the underline runtimes support it.
> First shot would be to add an adapter that allows m2eclipse controlled projects to activate the seam features.
> That would allow us still to bundle JBoss Tools without any dependencies to m2eclipse which still seem to drag in non-compatible plugins which we need to look into before tying us to m2eclipse.

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