[jbosstools-issues] [JBoss JIRA] (JBDS-2851) Team Usability

[Michelle Murray (JIRA)]

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

Michelle Murray edited comment on JBDS-2851 at 1/15/14 6:31 PM:
----------------------------------------------------------------

[~burrsutter], when you say eGit "out of the box", do you mean that eGit is packaged as part of JBDS installations? If eGit is essential for using OpenShift then we can document some instructions. From the examples given in the description, we could document how to:
* import a git project in preparation for deploying it to OpenShift
* once deployed on OpenShift, check in changes without necessarily publishing to OpenShift
* view git commit history for app deployed on OpenShift

Notice how these are very OpenShift and git centric. [~burrsutter] and [~adietish], what other tasks do users need to be able to perform?




                
      was (Author: mmurray):
    [~burrsutter], when you say eGit "out of the box", do you mean that eGit is packaged as part of JBDS installations? If eGit is essential for using OpenShift then we can document some instructions. From the examples given in the description, we could document how to:
* import a git project in preparation for deploying it to OpenShift
* once deployed on OpenShift, check in changes without necessarily publishing to OpenShift

Notice how these are very OpenShift and git centric. [~burrsutter] and [~adietish], what other tasks do users need to be able to perform?




                  
> Team Usability
> --------------
>
>                 Key: JBDS-2851
>                 URL: https://issues.jboss.org/browse/JBDS-2851
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: requirements
>            Reporter: Burr Sutter
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.  
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.  

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