October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21034) new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-21034: ----------------------------------- Summary: new Runtime detector fails to use default (ext-pt) enablement if user has previouslymodified enablement list Key: JBIDE-21034 URL: https://issues.jboss.org/browse/JBIDE-21034 Project: Tools (JBoss Tools) Issue Type: Bug Components: runtime-detection Affects Versions: 4.3.0.Final Reporter: Rob Stryker Small coding error causes a new runtime detector to not have its default enablement respected if a user has previously modified the enablement of any detector. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20990: --------------------------------------------- [~burrsutter] btw. if we could avoid having different names for this thing in community vs product that would be great - i.e. its ADB in community and CDK in product. Would be good if we could have a common name to refer to it. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-21033: -------------------------------------- https://github.com/jbosstools/jbosstools-integration-tests/pull/1221 > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-21033: ------------------------------------ Summary: Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test Key: JBIDE-21033 URL: https://issues.jboss.org/browse/JBIDE-21033 Project: Tools (JBoss Tools) Issue Type: Task Components: qa Affects Versions: 4.3.0.Final Reporter: Len DiMaggio -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21033) Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21033?page=com.atlassian.jira.plugi... ] Len DiMaggio reassigned JBIDE-21033: ------------------------------------ Assignee: Len DiMaggio > Add SmokeSuite to org.jboss.tools.mylyn.ui.bot.test > --------------------------------------------------- > > Key: JBIDE-21033 > URL: https://issues.jboss.org/browse/JBIDE-21033 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: qa > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Len DiMaggio > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20990) Add "CDK Server" for start/stop for the CDK

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20990?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20990: ------------------------------------- Everything here is PoC for now. None of these strings are permanent until they're in a GA release... and even then I'd imagine they can be changed with some annoyance to docs team. > Add "CDK Server" for start/stop for the CDK > ------------------------------------------- > > Key: JBIDE-20990 > URL: https://issues.jboss.org/browse/JBIDE-20990 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > > We want to be able to start/stop CDK easily. > Current suggestion is to use a server entry in server view that can start/stop vagrant by simply knowing its file location would be a good start. > note: the vagrant image might already be running so just need to be able to take care of that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3551) JavaEE Developer - be able to start/stop applications on docker with debug on/off

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3551?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3551: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > 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: docker > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3552) Developer - be able to incrementally deploy changes to docker containers

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3552?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3552: --------------------------------- Fix Version/s: 9.1.0.Beta1 10.0.0.Alpha1 > 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 > Fix For: 9.1.0.Beta1, 10.0.0.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3550) Developer - autodetect the CDK in IDE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3550?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3550: --------------------------------- Fix Version/s: 9.0.1.Beta1 10.0.0.Alpha1 > 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 > Fix For: 9.0.1.Beta1, 10.0.0.Alpha1 > > > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3549) Developer - start and stop the CDK easily from within the IDE

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3549?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3549: --------------------------------- Fix Version/s: 10.0.0.Alpha1 > 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, 10.0.0.Alpha1 > > > 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

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2015