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

[Max Rydahl Andersen (JIRA)]

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

Max Rydahl Andersen commented on JBIDE-3874:
--------------------------------------------

Snjezana,  cool demo.

About run on server we might be able to fix that locally. Did you report a bug at eclipse about it yet ?

Other "issues"/questions I have:
 * What are that M2 Capabilities on the maven install page ? That is just id's for the current project ? 
 * Is packaging choices the right thing to have on the maven page ? If yes, we should have it in sync with the packaging chosen on the seam (and other possible names)
 * Why is Seam listed on the M2 capabilities page ? Should it care at this point ?
 * Couldn't we somehow let Seam use the library provider mechanism JSF does and then delegate that to the M2ClasspathProvider and simply just have ui show up that ask you for JSF and Seam artifact id's ?
 * And yes, as Eugene asks....does this run from the command line too ?

Eugene,
What does "update project configuration action" actually do ? Read pom.xml and call out to the m2eclipse extension point implementors about enabling/disabling features or ?
(I assume import would be the same ?)


> 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