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

[Eugene Kuleshov (JIRA)]

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

Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------

Max, you are absolutely correct. More over, if you'll be using custom facets, the m2eclipse won't be able to transparently configure standard WTP facets and natures and project can have issues with classpath for unit tests, runtime and cross project dpeendencies at the compile time. It already handles the standard WTP projects out of the box, so you may not need to add anything special. Though you could perhaps add some custom natures/facets if pom.xml declares dependencies on something like Seam.

Please also note that using the m2eclipse project configuration framework will give you an additional advantage in the future, e.g. provide functionality to update pom.xml from the Eclipse project configuration.

So, I strongly advise to look at m2eclipse extension points for project configuration and its use cases [1], but if you find any limitations, the project configuration framework can be extended. One area for improvement is perhaps to provide a better support for the faceted project wizard (currently we recommend to use "Maven Project" wizard instead), see for example [2].

[1] http://docs.codehaus.org/display/M2ECLIPSE/Extension+Points+and+API#ExtensionPointsandAPI-Projectconfiguration(since0.9.4)
[2] http://docs.codehaus.org/display/M2ECLIPSE/WTP+mini+howto

> 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