[jbosstools-issues] [JBoss JIRA] (JBDS-3285) Git: Easy Import
Len DiMaggio (JIRA)
issues at jboss.org
Wed Mar 25 09:17:19 EDT 2015
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13053341#comment-13053341 ]
Len DiMaggio edited comment on JBDS-3285 at 3/25/15 9:16 AM:
-------------------------------------------------------------
Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse?
What we want is to be able to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.)
was (Author: ldimaggio):
Isn't the issue here that there are problems importing non-eclipse projects (those with zero eclipse meta data) into Eclipse?
Can we get a tool to examine a project and make a best guess at the project type (e.g., if there is a pom.xml file, then it's a maven project, etc.)
> Git: Easy Import
> ----------------
>
> 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
>
>
> 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)
More information about the jbosstools-issues
mailing list