[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
[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
[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
[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
[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
[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
[JBoss JIRA] (JBDS-3547) Eloqua tracking of Eloqua tracked links
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3547?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3547:
----------------------------------
OK, so then my PR should be fine, as it's basically just one simple global substitution:
{code}s#http://www.redhat.com/j/elqNow/elqRedir.htm?ref=http#https#g{code}
https://github.com/jbosstools/jbosstools-website/pull/524
Please approve and push to prod if you're satisfied w/ the PR and the above explanation, [~akazakov].
> Eloqua tracking of Eloqua tracked links
> ---------------------------------------
>
> Key: JBDS-3547
> URL: https://issues.jboss.org/browse/JBDS-3547
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: website
> Affects Versions: 9.0.0.GA
> Reporter: David Hladky
> Assignee: Alexey Kazakov
> Fix For: 7.1.1.GA, 8.0.0.GA, 8.1.0.GA, 8.1.1.GA, 9.0.0.GA, 9.1.0.Beta1
>
>
> I noticed, that all [downloads|http://tools.jboss.org/downloads] have Eloqua tracking link added. This is wrong, because Download Manager also adds Eloqua tracking, so each download goes through the Eloqua twice.
> I also noticed, that "http" is used in the links which should be replaced with "https". Apache does the redirect, but it is one unnecessary redirect in the process.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21028) Empty Hibernate Console Configuration dialog
by Koen Aers (JIRA)
Koen Aers created JBIDE-21028:
---------------------------------
Summary: Empty Hibernate Console Configuration dialog
Key: JBIDE-21028
URL: https://issues.jboss.org/browse/JBIDE-21028
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: hibernate, upstream
Affects Versions: 4.2.0.Alpha2
Environment: JBT 4.2.0.Alpha2 (on Eclipse Luna M5), L64, Fedora 19, OpenJDK 1.7
Reporter: Jiri Peterka
Assignee: Koen Aers
Fix For: 4.4.0.Alpha1
There is empty "Create Hibernate Console" dialog
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years