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

Eugene Kuleshov (JIRA) jira-events at lists.jboss.org
Fri Jun 19 08:52:00 EDT 2009


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

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

> mvn clean install works from the command line when 
> using maven 2.0.9 and 2.1.0. Run As>Maven clean/install 
> doesn't work when using Embedded or External 2.0.9/2.1.0 
> maven installations.
> There is a bug in m2eclipse http://jira.codehaus.org/browse/MNGECLIPSE-1173 
> and in JBoss > Tools https://jira.jboss.org/jira/browse/JBIDE-3456 
> related to this issue.

Ah, that is because maven-war-plugin and maven-ear-plugin can't handle "workspace resolution" when running build from Eclipse. I was planning to patch war/ear plugins to handle it but haven't got time yet.

The workaround is either disable workspace resolution for ear/war on Maven properties page in the project properties ("Run as / Maven install" and other predefined shortcuts inherit that setting), or crate explicit launch configuration using "Run as / Maven ..." and disable workpsace dependency resolution in there.

Sorry, I don't have jboss ide, nor jboss sample projects, can you please attach it to a jira issue?

> 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