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

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Thu Apr 9 09:01:26 EDT 2009


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

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

Some of the ways to make the Maven integration are the following:

1) using a Maven archetype or materializing Maven project (http://www.sonatype.com/books/m2eclipse-book/reference/eclipse-sect-materializing-project.html). I suppose it is possible to create the complete mavenized JBoss Seam project this way. In this case, there is nothing necessary to do within JBoss Tools because m2eclipse can import the archetype or materialize maven project. 

2) adding Maven capabilities to the existing JBoss wizard. I have proposed M2 facet for this functionality. It is possible to do this in some other way, but WTP Faceted Framework already has ability to add, remove and change the facet which wouldn't be trivial to do from scratch.

Max,

Is it planned the maven integration to be compatible with Ganymede?
WTP 3.1 has a new library framework that can be of use if the Ganymede compatibility is not required.
Would we support all the Seam versions (1.2, 2.0, 2.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

        



More information about the jbosstools-issues mailing list