[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=12472749#action_12472749 ] 

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

> The Maven classpath container doesn't contain all the libraries that are 
> contained in Server Runtime containers. That's why I added a possibility 
> to let users to not remove WTP classpath containers. 

Now I am confused. The Maven classpath container can contain any libraries, as long as they are declared in the pom.xml. If your project will use libraries that are not declared in the pom.xml you have a good chance that command line Maven build is not going to work for such project.

> 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