[JBoss JIRA] (JBDS-2865) Support downloadable cartridges in OpenShift UI
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2865?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2865:
--------------------------------------
Sprint: Sprint to 31.03.14
> Support downloadable cartridges in OpenShift UI
> -----------------------------------------------
>
> Key: JBDS-2865
> URL: https://issues.jboss.org/browse/JBDS-2865
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Affects Versions: 7.1.0.GA
> Reporter: Andre Dietisheim
> Assignee: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 8.0.0.GA
>
> Attachments: add-cartridge-1.png, new-application-1.png
>
>
> OpenShift now allows users to provide their own cartridges (standalone and embeddable ones). In both cases the user simply provides an url to a git repository.
> * use downloadable (standalone-, web-) cartridge for new application:
> !new-application-1.png!
> * use downloadable (embeddable-, add-on-) cartridge:
> !add-cartridge-1.png!
--
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
12 years, 2 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2851:
--------------------------------------
Epic Name: Team Usability
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> 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
12 years, 2 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen updated JBDS-2851:
--------------------------------------
Issue Type: Epic (was: Feature Request)
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Priority: Critical
> Labels: QE_JBDS80_needinfo
>
> 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
12 years, 2 months