[
https://issues.jboss.org/browse/JBIDE-13007?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-13007:
-------------------------------------
Assuming your project inherits the proper extension plugin that supports your custom
packaging, doing "Update Project" is the proper/expected way to tell m2e to kick
a new project configuration round.
Can we close this issue?
Maven custom packaging types fail after version/coordinate change.
Project files must be deleted and re-imported.
-----------------------------------------------------------------------------------------------------------------
Key: JBIDE-13007
URL:
https://issues.jboss.org/browse/JBIDE-13007
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 4.0.0.Alpha2
Reporter: Lincoln Baxter III
Assignee: Fred Bricon
Attachments: Screen Shot 2012-11-07 at 10.38.03 AM.png
When using custom packaging types, assuming the packaging plugin is resolved correctly,
the configuration works fine. However, after changing the packaging type coordinates, the
plugin is no longer correctly configured, and the project must be completely deleted
(eclipse .settings, .project/ and .classpath files) in order to correctly re-configure the
project.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira