[jbosstools-issues] [JBoss JIRA] (JBDS-3285) Git: Easy Import
Burr Sutter (JIRA)
issues at jboss.org
Tue Feb 17 10:56:49 EST 2015
[ https://issues.jboss.org/browse/JBDS-3285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13040973#comment-13040973 ]
Burr Sutter commented on JBDS-3285:
-----------------------------------
First, I did not make up this "easy import" feature - it was described in the Brno meeting, I forgot who was its originator.
Second, we have had serious complaints about SVN and Git import, Eclipse makes this process fairly challenging for the non-Eclipse expert.
UI options:
http://screencast.com/t/Bqkq9mK44k
http://screencast.com/t/Ahyj9jX8
http://screencast.com/t/D7vingjig
Examples of what to import:
https://github.com/javaee-samples/javaee7-samples
Note: these have pom.xml files but NO eclipse meta-data files
and WFK quickstarts, should also have no eclipse meta-data files
https://github.com/jboss-developer/jboss-wfk-quickstarts/tree/2.7.0.Final
> 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: Burr Sutter
> Labels: usability
> Fix For: 9.0.x
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
More information about the jbosstools-issues
mailing list