[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-4736) Add m2eclipse project-configurator for Seam projects

[ https://jira.jboss.org/jira/browse/JBIDE-4736?page=com.atlassian.jira.plu... ] Snjezana Peco resolved JBIDE-4736. ---------------------------------- Resolution: Done I have added this feature. The view folder is web content folder from the WAR project, the source folder is the first Eclipse source folder. If there is a folder containing "hot" in the name, it will be chosen as the action source folder. Package is the first package that has children or doesn't have any subpackage. Maven configurators are called aggressively. The Seam Maven configurator is called when importing a project, changes pom.xml and/or calls Maven>Update Project Configuration. Since we don't know if the settings is changed by the user or by the Seam configurator, I have done the following: If the user changes settings using the Seam Project preference page, the preference settings.changed.by.user will be set. If it is set, the Maven Seam configurator isn't called and the user's settings isn't changed. There is a similar problem in the m2eclipse's WTP configurator. It is not possible to change EAR's module using the JEE Module Preference page because the Maven WTP EAR configurator reconfigures the module based on pom.xml. There isn't any UI to change the settings.changed.by.user preference. I am not sure if we need to add this functionality to the Seam Settings Preference page for Maven projects. I have previewed the thread. There isn't any better solution than generating these files. I also propose that to be controlled by a preference. Another solution is that the JBT deployer recognizes a maven project, generates and deploys these files if necessary without adding them to the project's tree. However, this solution will work only for the JBT deployer, not for WTP deployers and/or for exporting EAR files. I have created JBIDE-4809 to track this issue. -- 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