[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3874) Maven integration
[
https://jira.jboss.org/jira/browse/JBIDE-3874?page=com.atlassian.jira.plu...
]
Eugene Kuleshov commented on JBIDE-3874:
----------------------------------------
The project can be run from the command line using maven 2.0.9
(probably 2.0.10),
but can't using Run As>Maven clean/Run As>Maven install.
The problem is that m2eclipse uses maven 2.1 that is not compatible with maven 2.0
If that is actually the case, then you found incompatibility in Maven 2.1/3.0, so please
report it to the Maven and/or m2eclipse JIRA.
However, it could be also an issue with the pom.xml you generated. For example you should
always specify versions of plugins you are using, especially the maven-war-plugin.
Also, it is misleading to say that "Run As>Maven ..." don't work, as
compared to Maven 2.0.9 from the command line. Because that shortcut can be configured to
use any version of Maven you want, including 2.0.9
As to Maven > Update project configuration action, it changes the
project.
For example, if there is the following configuration within the WAR project :
<plugin>
<artifactId>maven-war-plugin</artifactId>
<configuration>
<webappDirectory>${basedir}/WebContent</webappDirectory>
<warSourceDirectory>${basedir}/WebContent</warSourceDirectory>
</configuration>
</plugin>
Update project configuration will unecessary create a directory that will depend on the
workspace (something similar as <workspace>/WebContent). This is
a bug in
m2eclipse because the Update project configuration action doesn't check
if the URL is in the workspace, but treats it relative to the
workspace.
See https://jira.jboss.org/jira/browse/JBIDE-4413
Please report all bugs you found to m2eclipse JIRA. Though your description is somewhat
confusing, so it would be really helpful if you provide a reproducible test case.
It is also worth to say that it is a good idea to generate projects using common maven
conventions. For example, use the src/main/webapp as a web app directory
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