[jbosstools-issues] [JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import since it lets mvn overrule .project

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13077331#comment-13077331 ] 

Max Rydahl Andersen commented on JBIDE-19810:
---------------------------------------------

easy import should not start do *anything* with projects before it given the user a chance to verify what will happen.
this cannot be handled by treating m2e in a special way.

Suggestion is that we do an initial scan and show what is about to happen (like import project X, Z and Z as maven projects) and user can then press next/finish to "accept" things might take some time.

mylyn does not work as maven import - should be imported strictly as eclipse projects.

> 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)