[
https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-19810:
----------------------------------------
What takes too much time while importing is the dependency resolution for Maven (which is
not necessary at that time). I'll try to refactor it in a way that only minimal
necessary operations are performed while importing, and dependency resolution happens as a
separate job.
Using JBDS 9.0.0.Beta2 and importing
git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git , I find the result correct
(but since I don't know much about that project, that's not a strong assumption).
Can you elaborate on what you think is wrong in the output?
easymport is slow and wrong compared to basic import since it lets
mvn overrule .project
----------------------------------------------------------------------------------------
Key: JBIDE-19810
URL:
https://issues.jboss.org/browse/JBIDE-19810
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: easymport
Reporter: Max Rydahl Andersen
Priority: Critical
Fix For: 4.3.0.Beta2
when using
git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has
tons of projects with .project in it but also pom.xml. Resulting in slow and eventually
wrong imported projects.
This import is *really* slow with easyimport vs just using plain file import.
Shouldn't easyimport honor existing .project files over presence of a pom.xml (or
anything else) ?
If not could we allow users to disable certain configurators for an import or even
reorder priority so mvn wont win ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)