[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3874) Maven integration
[
https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plu...
]
Snjezana Peco commented on JBIDE-3874:
--------------------------------------
> 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.
Disabling workspace resolution for all the projects (ear, war, ejb
and parent) helps.
The Run As>Maven install action works, but deploying the application to the JBoss
server doesn't work if the workspace resolution is disabled (application.xml isn't
created; the ejb and web module are packaged).
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