[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=12460826#action_12460826 ] 

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

M2eclipse Maven project has a specific Maven nature (org.maven.ide.eclipse.maven2Nature), Maven builder (org.maven.ide.eclipse.maven2Builder), Maven classpath container (org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER) and the pom.xml file. m2eclipse can't work without this builder and nature. 
When I was talking about the Maven nature, builder and classpath container, I thought about those that are provided (and required) by m2eclipse. We wouldn't create a new nature, builder and/or classpath container. We would just add a new M2 facet. It is possible to do that in some other way, but, in my opinion, the Faceted framework is the easiest and most flexible. 

If we would use m2eclipse extension points for a project configuration, we would be limited to the Maven Project Wizard. I suppose we would like to create mavenized JBoss Tools projects (Seam, Portlet, Web Services, ESB ...) using the existing JBoss Tools/WTP wizards.
I also think it is possible to add Maven classpath container to JSF, JPA and other existing WTP facets (if using WTP 3.1).

> 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
>            Priority: Critical
>             Fix For: 3.1.0
>
>
> 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