[jbosstools-issues] [JBoss JIRA] (JBIDE-13703) Team - Verify the workflow

[Max Rydahl Andersen (JIRA)]

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

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

not sure where we could/would do this (i.e. a "Import Project" with smarter detection to know which import type and features to enable..ie. svn/git etc.. Starting with central - might be better fit in base though.


                
> Team - Verify the workflow
> --------------------------
>
>                 Key: JBIDE-13703
>                 URL: https://issues.jboss.org/browse/JBIDE-13703
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: central, common/jst/core
>            Reporter: Burr Sutter
>            Assignee: Fred Bricon
>         Attachments: JBDS-usability.pdf, Netbeans-Open-project.PNG
>
>
> The average end-user would like to:
> 1) check out (clone) a project from CVS, SVN or Git
>  -- add repo, navigate repo, check out a project
>  -- project may or may not have .classpath, .project or .settings files
>  -- project may be Maven-based
> and see if the following work
> 2) Are the appropriate facets enabled?
> 3) Does it build immediately?
> 4) Can I immediately hit the run button to launch it on my app server?
> 5) Can I immediately hit the debug button to debug it on my app server?
>  -- how do I step if there are no break points?
> 6) Make a change to a file, re-run/debug again
> 7) Run JUnit tests
> 8) Check the change back into the repo with comments

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira