[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:
-----------------------------
Component/s: jsp/jsf/xml/html-source-editing
> 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: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: jsp/jsf/xml/html-source-editing
> Reporter: Max Rydahl Andersen
>
> 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
(v6.4.11#64026)
10 years, 5 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 reassigned JBDS-3551:
--------------------------------
Assignee: Alexey Kazakov
> 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: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: jsp/jsf/xml/html-source-editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
>
> 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
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3550:
-----------------------------
Component/s: docker
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3550:
--------------------------------
Assignee: Xavier Coulon
> Developer - autodetect the CDK in IDE
> -------------------------------------
>
> Key: JBDS-3550
> URL: https://issues.jboss.org/browse/JBDS-3550
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
>
> User Story:
> As a Developer on first startup after the installer have run, the CDK should be configured in the IDE and be ready to use
> Acceptance Criteria:
> * If the CDK is running there should be an openshift connection that is configured with the right url and username and users should have been given a password that allows him to connect
> * if the CDK is running there should be a docker connection that is configured with the right connetion info, certifcates etc. to connect
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3552:
-----------------------------
Component/s: docker
> Developer - be able to incrementally deploy changes to docker containers
> -------------------------------------------------------------------------
>
> Key: JBDS-3552
> URL: https://issues.jboss.org/browse/JBDS-3552
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
>
> User Story:
> As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly.
> Acceptance Criteria:
> * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment.
> * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh.
> * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source)
> * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3552:
--------------------------------
Assignee: Xavier Coulon
> Developer - be able to incrementally deploy changes to docker containers
> -------------------------------------------------------------------------
>
> Key: JBDS-3552
> URL: https://issues.jboss.org/browse/JBDS-3552
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
>
> User Story:
> As a Developer I want to be able to incrementally deploy changes to my running application without building from scratch so I can see changes quickly.
> Acceptance Criteria:
> * Once the initial application is deployed changes made in the IDE should be deployed over to the containers filesystem/deployment.
> * Changes that the runtime support to pickup dynamically (i.e. html/js for JavaEE) should take effect immediatly and be seen in a browser refresh.
> * Changes that the the runtime requires a restart for (i.e. class files) should take effect when restarting the application (which should not require a rebuild from source)
> * Same workflow should work for docker and openshift applications (but each might implement it differently using oc sync or docker rsync or volume mounts etc.)
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3549:
-----------------------------
Component/s: (was: server)
> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
> Key: JBDS-3549
> URL: https://issues.jboss.org/browse/JBDS-3549
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3549:
--------------------------------
Assignee: Xavier Coulon (was: Rob Stryker)
> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
> Key: JBDS-3549
> URL: https://issues.jboss.org/browse/JBDS-3549
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker
> Reporter: Max Rydahl Andersen
> Assignee: Xavier Coulon
> Fix For: 9.1.0.Beta1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3549:
-----------------------------
Component/s: docker
server
> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
> Key: JBDS-3549
> URL: https://issues.jboss.org/browse/JBDS-3549
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker, server
> Reporter: Max Rydahl Andersen
> Fix For: 9.1.0.Beta1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ]
Nick Boldt reassigned JBDS-3549:
--------------------------------
Assignee: Rob Stryker
> Developer - start and stop the CDK easily from within the IDE
> -------------------------------------------------------------
>
> Key: JBDS-3549
> URL: https://issues.jboss.org/browse/JBDS-3549
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Story
> Components: docker, server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Fix For: 9.1.0.Beta1
>
>
> User Story:
> As a Developer I should be able to start and stop the CDK easily from within the IDE without having to know about internal details like vagrant or command line tools so I can get started quickly.
> Acceptance Criteria:
> * If CDK is not running, clicking start should bring up the CDK and I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running already, clicking start should recognize that and not try to stop/halt it and then I should be able to use the docker and openshift tooling against the CDK from Eclipse
> * If CDK is running, clicking stop should halt the CDK and docker
> * When stopped, the docker and openshift configuraton should still stay in Eclipse, but should not work and give sensible errors when/if failing.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months