April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3351: ----------------------------- CDW docs_ack: ? CDW devel_ack: ? CDW pm_ack: + CDW qa_ack: ? > Copyright notice refers to 2014, not 2015 > ----------------------------------------- > > Key: JBDS-3351 > URL: https://issues.jboss.org/browse/JBDS-3351 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Trivial > Fix For: 9.0.0.Alpha2 > > > The copyright notice for 9.0.0.Alpha1 reads: > ==================================== > Version: 9.0.0.Alpha1 > Build id: Alpha1-v20150216-1042-B11 > Build date: 20150216-1042 > Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved. > ==================================== > ------> Shouldn't this refer to 2004-2015? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3351) Copyright notice refers to 2014, not 2015

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3351?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3351: ---------------------------------- Updated files in JBDS: {code} modified: features/com.jboss.devstudio.core.feature.source/feature.properties modified: features/com.jboss.devstudio.core.feature/feature.properties modified: installer/src/config/resources/EULA/JBoss-EULA.html modified: installer/src/test/com/jboss/devstudio/core/installer/IUListPanelTest.java modified: plugins/com.jboss.devstudio.core.usage.branding/about.properties modified: plugins/com.jboss.devstudio.core/about.html modified: plugins/com.jboss.devstudio.core/about.properties modified: plugins/com.jboss.devstudio.core/plugin.properties modified: site/com.jboss.devstudio.core.product {code} https://github.com/jbdevstudio/jbdevstudio-product/commit/bdf9459bd8722ab... > Copyright notice refers to 2014, not 2015 > ----------------------------------------- > > Key: JBDS-3351 > URL: https://issues.jboss.org/browse/JBDS-3351 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build, installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Trivial > Fix For: 9.0.0.Alpha2 > > > The copyright notice for 9.0.0.Alpha1 reads: > ==================================== > Version: 9.0.0.Alpha1 > Build id: Alpha1-v20150216-1042-B11 > Build date: 20150216-1042 > Copyright (c) 2004-2014 Red Hat, Inc., contributors and others. All rights reserved. > ==================================== > ------> Shouldn't this refer to 2004-2015? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19025 at 4/15/15 5:18 PM: ------------------------------------------------------------- We now have 2 update sites for Central and 2 for Early Access: * Central Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/ * Central TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ * Early Access Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m... * Early Access TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/ This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA, built here [1]: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery... was (Author: nickboldt): We now have 2 update sites for Central and 2 for Early Access: * Central Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/ * Central TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ * Early Access Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m... * Early Access TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/ This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-19025 at 4/15/15 5:17 PM: ------------------------------------------------------------- We now have 2 update sites for Central and 2 for Early Access: * Central Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/central/master/ * Central TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ * Early Access Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: http://download.jboss.org/jbosstools/mars/snapshots/updates/earlyaccess/m... * Early Access TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/ This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient. was (Author: nickboldt): We now have 2 update sites for Central and 2 for Early Access: * Central Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: * Central TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ * Early Access Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: * Early Access TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/ This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19025) Separate JBT and JBDS Central and EA sites

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19025?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-19025: ------------------------------------ We now have 2 update sites for Central and 2 for Early Access: * Central Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: * Central TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtcentraltarget/ * Early Access Update Site (contains only things from JBT) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-sit... ** Output: * Early Access TP (third party stuff) ** Job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-centralta... ** Output: http://download.jboss.org/jbosstools/targetplatforms/jbtearlyaccesstarget/ This results in discovery sites for JBT Central, JBT EA, JBDS Central, and JBDS EA: http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... So now when things change in JBT, they're rebuilt into an *update site* instead of affecting a *target platform*, which will make our release process more efficient. > Separate JBT and JBDS Central and EA sites > ------------------------------------------ > > Key: JBIDE-19025 > URL: https://issues.jboss.org/browse/JBIDE-19025 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: discovery > Affects Versions: 4.2.2.Final > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > Currently, we have to repeat (and update very often) some JBT artifacts in the Central .target files because JBDS needs them. > This adds some long steps to the JBT staging process ( https://github.com/jbdevstudio/jbdevstudio-devdoc/blob/master/release_gui... ), whereas this is a JBDS need. > So we should split the content of Central/EA update sites for JBT and JBDS, and have them separated in distinct .target files: a Central/EA couple for JBT and another Central/EA couple for JBDS. JBDS only would add the necessary addition that are part of JBT but not part of JBDS. > Since we're there, it would even be cleaner to have those artifacts in distinct repo, so that JBDS wouldn't leak in JBT. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- Cool. So should install-grinder jobs be changed to use http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... and https://devstudio.jboss.com/9.0/snapshots/builds/jbosstools-discovery.cen... ? > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19473) Central can't load Discovery catalog

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19473?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-19473. ------------------------------ I've fixed the jobs to use the correct new publishing locations. Details here: https://issues.jboss.org/browse/JBDS-3208?focusedCommentId=13059479&page=... Closing. Reopen if symptoms reappear. :D > Central can't load Discovery catalog > ------------------------------------ > > Key: JBIDE-19473 > URL: https://issues.jboss.org/browse/JBIDE-19473 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery > Affects Versions: 4.3.0.Alpha2 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > Both locally and with install-grinder, after installing nighly build from master, Central compains about "no connectors" found. > The URL of the catalog seems right ( http://download.jboss.org/jbosstools/discovery/nightly/core/master/jbosst... ), referenced plugins are existing and seem to have right content. > Log says > {quote} > !ENTRY org.eclipse.mylyn.discovery.core 4 0 2015-03-19 10:22:00.223 > !MESSAGE Unknown category 'org.jboss.tools.central.discovery.a.web' referenced by connector 'angularjs-eclipse-feature' declared in org.jboss.tools.central.discovery.earlyaccess_4.3.0.Alpha2_v20150318_0819_B3421.jar_8982963591780016496.jar > {quote} > I looked at jbosstoold-discovery history to see whether there was a suspicious change since last success (March 13th for install-grinder) and couldn't see anything related. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3208: ---------------------------------- I've fixed the jobs [1], [2] to use the correct new publishing locations, INCLUDING fixing jbosstools-cleanup.sh [3], [4] so it works for devstudio.redhat.com /builds/ folders too [3], [4]. [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery... [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-discovery... [3] https://github.com/jbosstools/jbosstools-build-ci/commit/bf4e07ffd4a1291a... [4] https://github.com/jbosstools/jbosstools-build-ci/commit/e14086feeed1abb7... [5] https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ce... [6] https://devstudio.redhat.com/9.0/snapshots/builds/jbosstools-discovery.ea... Also updated ide-config.properties [7] to pull from the new correct paths [8], [9]: [7] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/10b7cd... [8] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... [9] http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-dis... And I've prepared new paths on devstudio.redhat.com, such as [10], [11], so we'll be ready for Alpha2 publishing to the new path conventions: [10] https://devstudio.redhat.com/9.0/snapshots/updates/ [11] https://devstudio.redhat.com/9.0/staging/updates/ > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > Latest suggestion: > * /\{mars,9.0}/ > ** /\{{color:red}snapshots{color},{color:orange}staging{color},{color:blue}development{color},{color:green}stable{color}\}/ > *** /*updates*/ > **** /\{requirements, jbosstoolstarget,jbdevstudiotarget, core,coretests,webtools,hibernatetools, discovery, central,earlyaccess, integration-stack,integration-stack-earlyaccess}/ > ***** /<build-version = 4.3.0.Alpha1, 4.3.0.Final, 4.41.\*, 4.50.\*...>/ > *** /*builds*/ > **** /<job-name>/ > ***** /{<pull-request-version = PR123, PR124, PR125...>, <build-version = B123, B124, B125...>}/ > --- > Older idea: > {code} > <download.jboss.org,devstudio.redhat.com> > <earlyaccess,updates,discovery>/<mars,9.0> > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/<mars,9.0>/stable is a pointer back into parent folder so published URL can be simpler > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last N builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19601) Explorer: Resources cannot be listed when using latest OpenShift origin v3 code

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19601?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19601: ------------------------------------- Steps to Reproduce: # ASSERT: make sure you're using the latest openshift origin code from github (https://github.com/openshift/origin.git) # EXEC: create a new connection (with the credentials that you have set to the server) and hit "Finish" # ASSERT: the connection dialog closes Result: You get an error dialog popping up telling you that the connection was refused !connection-refused.png! In the Eclipse log one can see the following stack trace: {code} java.lang.RuntimeException: java.lang.RuntimeException: Version 'v1beta3' not supported for kind 'Status' at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:111) at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:95) at com.openshift.internal.restclient.DefaultClient.handleHttpClientException(DefaultClient.java:354) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:116) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:97) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:92) at org.jboss.tools.openshift.core.connection.Connection.get(Connection.java:265) at org.jboss.tools.openshift.internal.ui.explorer.OpenShiftExplorerContentProvider.getChildrenFor(OpenShiftExplorerContentProvider.java:67) at org.jboss.tools.openshift.internal.common.ui.explorer.BaseExplorerContentProvider$1.run(BaseExplorerContentProvider.java:124) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) Caused by: java.lang.RuntimeException: Version 'v1beta3' not supported for kind 'Status' at com.openshift.internal.restclient.model.properties.ResourcePropertiesRegistry.get(ResourcePropertiesRegistry.java:135) at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:107) ... 9 more {code} was: # ASSERT: make sure you're using the latest openshift origin code from github (https://github.com/openshift/origin.git) # EXEC: create a new connection (with the credentials that you have set to the server) and hit "Finish" # ASSERT: the connection dialog closes Result: You get an error dialog popping up telling you that the connection was refused !connection-refused.png! > Explorer: Resources cannot be listed when using latest OpenShift origin v3 code > ------------------------------------------------------------------------------- > > Key: JBIDE-19601 > URL: https://issues.jboss.org/browse/JBIDE-19601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > Attachments: connection-refused.png > > > When using the latest origin code from github one can connect but once the connection wizard is closed an error dialog pops up telling you that the connection was refused -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19601) Explorer: Resources cannot be listed when using latest OpenShift origin v3 code

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19601?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19601: ------------------------------------- Attachment: connection-refused.png > Explorer: Resources cannot be listed when using latest OpenShift origin v3 code > ------------------------------------------------------------------------------- > > Key: JBIDE-19601 > URL: https://issues.jboss.org/browse/JBIDE-19601 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > Attachments: connection-refused.png > > > When using the latest origin code from github one can connect but once the connection wizard is closed an error dialog pops up telling you that the connection was refused -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 12 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 April 2015