December 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23614) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [livereload]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23614?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23614. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [livereload] > -------------------------------------------------------------------- > > Key: JBIDE-23614 > URL: https://issues.jboss.org/browse/JBIDE-23614 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: livereload > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [livereload]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for livereload task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23613) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [jst]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23613?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23613. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [jst] > ------------------------------------------------------------- > > Key: JBIDE-23613 > URL: https://issues.jboss.org/browse/JBIDE-23613 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jst > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [jst]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md docs features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for jst task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23615) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [openshift]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23615?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23615. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [openshift] > ------------------------------------------------------------------- > > Key: JBIDE-23615 > URL: https://issues.jboss.org/browse/JBIDE-23615 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [openshift]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for openshift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23616) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [server]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23616?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23616. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [server] > ---------------------------------------------------------------- > > Key: JBIDE-23616 > URL: https://issues.jboss.org/browse/JBIDE-23616 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: server > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [server]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md all-tests archives as jmx pom.xml pom.xml.orig site wtp *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23617) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [visual-page-editor-core]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23617?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23617. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [visual-page-editor-core] > --------------------------------------------------------------------------------- > > Key: JBIDE-23617 > URL: https://issues.jboss.org/browse/JBIDE-23617 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: visual-page-editor-core > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [visual-page-editor-core]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for visual-page-editor-core task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23618) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [webservices]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23618?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23618. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [webservices] > --------------------------------------------------------------------- > > Key: JBIDE-23618 > URL: https://issues.jboss.org/browse/JBIDE-23618 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: webservices > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [webservices]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md docs features plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23619) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [integration-tests]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23619?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23619. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [integration-tests] > --------------------------------------------------------------------------- > > Key: JBIDE-23619 > URL: https://issues.jboss.org/browse/JBIDE-23619 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [integration-tests]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.md plugins pom.xml pom.xml.orig site tests *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for integration-tests task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23620) For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [central-update]

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23620?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-23620. ------------------------------ Resolution: Done > For JBIDE 4.4.3.AM1: Prepare for 4.4.3.AM1 / 10.3.0.AM1 [central-update] > ------------------------------------------------------------------------ > > Key: JBIDE-23620 > URL: https://issues.jboss.org/browse/JBIDE-23620 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central-update > Reporter: Friendly Jira Robot > Priority: Blocker > Labels: task > Fix For: 4.4.3.AM1 > > > For JBIDE 4.4.3.AM1 [central-update]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.AM1-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.AM1-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: README.adoc README.contributing.adoc README.discovery.sites.adoc build.xml jbdevstudio jbosstools jbtcentraltarget jbtearlyaccesstarget pom.xml pom.xml.orig publish-assembly.xml *{color:orange}4.4.3.AM1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for central-update task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4197) sign devstudio rpm & document the process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4197?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4197: ---------------------------------- Link to request from 3 years ago (blocked by sec ops / no dedicated hardware) to sign jbosstools / devstudio jars themselves: https://issues.jboss.org/browse/JBIDE-13407 > sign devstudio rpm & document the process > ----------------------------------------- > > Key: JBDS-4197 > URL: https://issues.jboss.org/browse/JBDS-4197 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.2.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 10.3.0.GA > > > For the GA build of the devstudio rpm, I need to: > * sign the rpm [1] > * document the steps in the release guide [2] > [1] https://engineering.redhat.com/docs/en-US/Policy/30.se/html/Security_Engi... > [2] https://github.com/jbdevstudio/jbdevstudio-devdoc/tree/master/release_gui... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23511) CDK start fails if you don't accept OpenShift certificate in time

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23511?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23511: --------------------------------------- {quote} This is such a minor issue and since ti applies to all server adapters, and can't be fixed, I'm just going to reject it. {quote} Fair enough. But I don't agree that it happens to all server adapters. I mean the way things work, sure. But not the end result - typically a server does not need any interaction from the user to complete the startup. So you can start eap and go your own way and it will always succeed (and besides, it will start really fast, so usually you'll see it through anyway). But with CDK, it takes several minutes to start AND it requires user interaction (accepting the cert) for the startup to succeed. Granted, you only need to accept the cert once on a new vagrant box, but who starts cdk more than once before destroying it? :-P > CDK start fails if you don't accept OpenShift certificate in time > ----------------------------------------------------------------- > > Key: JBIDE-23511 > URL: https://issues.jboss.org/browse/JBIDE-23511 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.Final > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > This happened to me a couple of times and it's pretty annoying, but I'm not sure if anything can be done about it. > When you launch cdk in devstudio and then forget about it and do something else, then when you get back to devstudio to actually play with cdk, you will see it fail horribly. > This is because the startup time out has been reached and since you haven't accepted the openshift certificate, the prompt will be waiting for you and will cause time out. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016