[jbosstools-issues] [JBoss JIRA] (JBDS-3285) Easy Import of non-eclipse projects

[Fred Bricon (JIRA)]

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

Fred Bricon commented on JBDS-3285:
-----------------------------------

I think there's a fundamental flaw in the easymport API : there's no configurator sort per priority. Each configurator should declare a weight/priority, so all of them could be sorted, then the first configurator (highest priority) that applies do its thing.
So then you can have :
Maven > PDE > generic project (.project) > projectless folder

If we had, say Gradle and Maven having the same priority, and both pom.xml and build.gradle are found, the UI should show the conflicting configurators and let the user decide how to import the project.


> Easy Import of non-eclipse projects
> -----------------------------------
>
>                 Key: JBDS-3285
>                 URL: https://issues.jboss.org/browse/JBDS-3285
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>          Components: requirements, upstream
>    Affects Versions: 8.0.0.GA
>            Reporter: Burr Sutter
>            Assignee: Mickael Istria
>              Labels: usability
>             Fix For: 9.0.0.Alpha2
>
>         Attachments: import-me.zip
>
>
> As a Java EE developer, in some cases using Git for the first time (or only familiar with command line git), I find it very difficult to clone and import a project correctly into JBDS, having the appropriate facets configured, if it has a maven pom.xml, correctly setting the build path, where it is easily deployable to a localhost EAP instance.  
> The mission here is to make the Git experience much more user friendly.
> Progress/Status (updated progressively): https://wiki.eclipse.org/E4/UI/Smart_Import



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)