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

Eugene Kuleshov (JIRA) jira-events at lists.jboss.org
Sat Jun 20 20:27:58 EDT 2009


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

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

That is right, so you can keep the project setting enabled, but have it disabled in the launch configuration. Alternatively, both could be disabled, but then you'll need to run "Maven install" action and then Project / Clean... before deploying. As I mentioned above it is not an easy issue to address in only m2eclipse and the easiest is to extend existing Maven plugins to handle this.

> 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

        



More information about the jbosstools-issues mailing list