[
https://issues.jboss.org/browse/JBIDE-14807?page=com.atlassian.jira.plugi...
]
Fred Bricon updated JBIDE-14807:
--------------------------------
Description:
Currently, after we import a maven project example, we run a maven update project right
after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerably, taking almost 50% longer to create a project from
central.
We should only trigger that project update if some "out of date" markers are
actually added on the project.
was:
Currently, after we import a maven project example, we run a maven update project right
after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerable, taking almost 50% longer to create a project from
central.
We should only trigger that project update if some "out of date" markers are
actually added on the project.
Don't maven update the project on maven example project import,
if not necessary
--------------------------------------------------------------------------------
Key: JBIDE-14807
URL:
https://issues.jboss.org/browse/JBIDE-14807
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: maven, project-examples
Affects Versions: 4.1.0.Beta1
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 4.1.0.Beta2
Currently, after we import a maven project example, we run a maven update project right
after, to prevent some random m2e out-of-date red markers from popping up.
That slows imports down considerably, taking almost 50% longer to create a project from
central.
We should only trigger that project update if some "out of date" markers are
actually added on 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