[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=12460675#action_12460675 ] 

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

Maven integration proposal:

1) creating an integration feature and plugin (org.jboss.tools.maven) that would depend on m2eclipse
The plugin would have a wtp facet (M2 facet) that would add maven artifacts to a project(s).
If Ganymede compatibility wouldn't be required for the Maven integration, we could integrate the M2 facet with a library provider framework (https://bugs.eclipse.org/bugs/show_bug.cgi?id=246448). We could add Maven library providers to the existing WTP facets (JSF, JPA...) in this way.

The M2 facet would add the Maven nature, builder, Maven classpath and the pom.xml file to a web project(s)
The plugin would contain pom.xml templates for different projects and versions (Seam 1.2, 2.x, Portlet 1.0, 2.0, web services...).

2) if the user has the integration plugin (and m2eclipse) installed, the Seam Project wizard would have the M2 facet enabled.
Seam install delegates would check for the existence of the M2 facet. If it exists, Seam libraries wouldn't be copied. Maven parent project would also be created similarly to the mavenized Seam examples.

3) the Portlet facets (and, maybe, Web Services facet) would also check for the existence of the M2 facet and add their dependencies to the pom.xml.
I suppose that the ESB wizard could have the "mavenized" option that would serve to add the M2 facet to the ESB project.
Re the BIRT facet, currently there is no any Maven repository that contains newer BIRT distributions (2.3, 2.5).

4) if the M2 facet would be added using the New Web Dynamic project wizard, it would add the Maven builder, nature, classpath and a simple pom.xml.
Other facets would add their dependencies to the pom.xml.

5) if the M2 facet would be added to an existing Web project, the user would get a list of libraries and classpath containers that could be removed.

6) if the M2 facet would be removed from the project, the Maven nature, builder and classpath would be removed, but the user would have to add required classpaths and libraries.

PS
m2eclipse plugins don't contain compile errors in Galileo.



> 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