[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 M2 facet page enables a user to add the following maven properties: groupId, artifactId, version, packaging, name and description If the project contains the Seam facet, the user can choose a maven version of Seam - 2.1.1.GA is the default for the Seam facet 2.1 and 2.0.2.SP1 for the Seam facet 2.0. The user can also decide whether to remove WTP classpath containers (where the path starts with org.eclipse.jst) possible names) In case of a Seam project, packaging is related to a web project and needs to be war - we can disable this field. The M2 facet recognizes that the project contains the Seam facet and enables the user to choose a Seam version. As to JSF, I am planning to add an extension point that would use WTP 3.1 Library Framework and provide contributions that would add dependencies to the M2 classpath container. Some facet would be able to use that extension point. The Seam project wizard is specific and is not easy to contribute in the Seam facet. The Seam facet doesn't use the WTP Library framework, but copies libraries from a Seam distribution. I have changed the wizard so that libraries aren't copied, but added to the M2 classpath container within the post install delegate. Post install delegate because we need to know properties of the Seam facet and JBoss Maven facet when adding these libraries to the M2 classpath container. The current Seam wizard is minimally changed this way. Seam requires more than JSF and Seam artifacts: hibernate, drools, richfaces, facelets ... we need versions of all of these artifacts. 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 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 There is also a problem to ensure the Import Maven Project action to work correctly. Namely, the root directory of the EAR project is EarContent. maven-ear-plugin (>=2.3) doesn't allow changing the resource directory. In order to fix the project to run from the command line, I have configured EarContent as the source directory and src/main/application (the default resource directory of maven-ear-plugin) as the output directory of the Eclipse project . Eclipse deploying, m2eclipse EAR configurator as well as mvn commands from the command line work correctly this way. However, Import Maven projects probably won't import the EarContent directory, WTP settings, Seam settings... -- 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