[jbosstools-issues] [JBoss JIRA] (JBIDE-11292) Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects
Burr Sutter (JIRA)
jira-events at lists.jboss.org
Tue Mar 13 10:07:47 EDT 2012
[ https://issues.jboss.org/browse/JBIDE-11292?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12676427#comment-12676427 ]
Burr Sutter commented on JBIDE-11292:
-------------------------------------
I wonder if it is because the archetypes have changed, after these projects were generated?
> Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-11292
> URL: https://issues.jboss.org/browse/JBIDE-11292
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Reporter: Burr Sutter
> Assignee: Fred Bricon
> Attachments: project_configuration_is_not_up_to_date_0.png
>
>
> "Project configuration is not up-to-date with pom.xml. Run project configuration update"
> I have noticed, with beta1e and perhaps beta1d, that when I load up my workspace with projects - created via the archetypes, quickstarts and even File Import - perhaps, after a restart of the IDE - the next time I import (file-import or archetype) another maven project, the previous projects throw up the project configuration error msg.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
More information about the jbosstools-issues
mailing list