[JBoss JIRA] (JBDS-3434) Kubernetes editor & wizard
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3434?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3434:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> Kubernetes editor & wizard
> --------------------------
>
> Key: JBDS-3434
> URL: https://issues.jboss.org/browse/JBDS-3434
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 8.x
> Reporter: Charles Moulliard
> Assignee: Jeff MAURY
> Fix For: 12.x
>
>
> To deploy a project on Openshift3, it will be required to edit/generate a kubernetes.json file. The fabric8 project has created a maven plugin to generate the kubernetes.json file and next to deploy the project on OS" (= maven fabic8:install) but it could be interesteting also that we propose :
> - a kubernetes editor within JBDS to update the YAML or JSON file and
> - a wizard to create a kubernetes template file using some criteria like the API version, name, ports to be exposed, volumes to mount, ...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3551:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> JavaEE Developer - be able to start/stop applications on docker with debug on/off
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3551
> URL: https://issues.jboss.org/browse/JBDS-3551
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 12.x
>
>
> User Story:
> As a JavaEE Developer I should be able to start/stop applications with debug turned on or off
> Acceptance Criteria:
> * Developer can start/stop an application from a central place, no CLI operations needed.
> * Developer can start with or without debug enabled
> * if necessary to restart when going from started to debugging or debugging to started the user should be asked if really want to restart
> * When debug is on the Java debugger should be connected and any enabled breakpoints when hit should show up in the debugger
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBDS-3523) Default toolbar is too long
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3523?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3523:
-----------------------------
Fix Version/s: 12.x
(was: 10.x)
> Default toolbar is too long
> ---------------------------
>
> Key: JBDS-3523
> URL: https://issues.jboss.org/browse/JBDS-3523
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Enhancement
> Components: ui/branding
> Affects Versions: 9.0.0.Beta2
> Reporter: ehsavoie Hugonnet
> Labels: new_and_noteworthy
> Fix For: 12.x
>
> Attachments: jbt-wtf_toolbar.png, netbeans_toolbar.png
>
>
> Per default the Toolbar has so many entries that it takes more than one line.
> Most of those are useless : other IDEs don't show that much per default maybe some cleanup is required
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months