March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21997) Aeri causes NPE when running unittests

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21997?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21997: ------------------------------------ P2diffs for the 4.52.x TPs are pretty obvious - 4 new IUs in, 4 old IUs out. {code} $➔ p2diff file://`pwd` http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... < org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160304-1116] < org.eclipse.epp.logging.aeri.core [1.100.0.v20160304-1116] < org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160304-1116] < org.eclipse.epp.logging.aeri.ide [1.100.0.v20160303-1450] > org.eclipse.epp.logging.aeri.core [1.100.0.v20160211-1103] > org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160217-0435] > org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160217-0435] > org.eclipse.epp.logging.aeri.ide [1.100.0.v20160217-0435] === Summary === file:///home/nboldt/tru/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 4 unique IUs http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains 4 unique IUs p2diff file://`pwd` https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1... < org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160304-1116] < org.eclipse.epp.logging.aeri.core [1.100.0.v20160304-1116] < org.eclipse.epp.logging.aeri.ide [1.100.0.v20160303-1450] < org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160217-0435] > org.eclipse.epp.logging.aeri.ide [1.100.0.v20160217-0435] > org.eclipse.epp.logging.aeri.core [1.100.0.v20160211-1103] > org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160217-0435] === Summary === file:///home/nboldt/tru/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo contains 4 unique IUs https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.52.0.CR1... contains 4 unique IUs {code} However, for the 4.50.2 TP, we see a change to jetty (9.2.9 -> 9.2.13 and something odd with the addition of the linux.ppc64le bundles. Not sure these changes are safe. {code} > org.eclipse.epp.logging.aeri.core [1.100.0.v20160211-1103] < org.eclipse.epp.logging.aeri.core [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.ide [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.ide [1.100.0.v20160303-1450] > org.eclipse.jetty.webapp [9.2.13.v20150730] < org.eclipse.jetty.webapp [9.2.9.v20150224] > org.eclipse.jetty.xml [9.2.13.v20150730] < org.eclipse.jetty.xml [9.2.9.v20150224] > org.eclipse.core.filesystem.linux.ppc64le [1.4.0.v20140822-1153] > org.eclipse.equinox.executable_root.gtk.linux.ppc64le [3.6.200.v20150602-1417] > org.eclipse.equinox.launcher.gtk.linux.ppc64le [1.0.300.v20150602-1417] === Summary === file:///home/nboldt/43x/targetplatforms/jbosstools/multiple/target/jbosstools-multiple.target.repo contains 6 unique IUs http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains 9 unique IUs > org.eclipse.epp.logging.aeri.core [1.100.0.v20160211-1103] < org.eclipse.epp.logging.aeri.core [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.feature.feature.group [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.feature.feature.jar [1.100.0.v20160304-1116] > org.eclipse.epp.logging.aeri.ide [1.100.0.v20160217-0435] < org.eclipse.epp.logging.aeri.ide [1.100.0.v20160303-1450] > org.eclipse.jetty.webapp [9.2.13.v20150730] < org.eclipse.jetty.webapp [9.2.9.v20150224] > org.eclipse.jetty.xml [9.2.13.v20150730] < org.eclipse.jetty.xml [9.2.9.v20150224] > org.eclipse.core.filesystem.linux.ppc64le [1.4.0.v20140822-1153] > org.eclipse.equinox.executable_root.gtk.linux.ppc64le [3.6.200.v20150602-1417] > org.eclipse.equinox.launcher.gtk.linux.ppc64le [1.0.300.v20150602-1417] === Summary === file:///home/nboldt/43x/targetplatforms/jbdevstudio/multiple/target/jbdevstudio-multiple.target.repo contains 6 unique IUs https://devstudio.redhat.com/targetplatforms/jbdevstudiotarget/4.50.2.CR1... contains 9 unique IUs {code} Can someone comment on these? > Aeri causes NPE when running unittests > -------------------------------------- > > Key: JBIDE-21997 > URL: https://issues.jboss.org/browse/JBIDE-21997 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aeri, target-platform > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.CR1 > > > an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling. > We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868 > Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103 > Please take care because the version number are both 1.100.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3736: ----------------------------------- As [~maxandersen] commented in https://github.com/jbosstools/jbosstools-base/pull/489#discussion_r55865552, it'd be better if we used cdk/ as root folder and silent detection worked recursively. [~rob.stryker]? > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3736: --------------------------------- Assignee: Rob Stryker (was: Denis Golovin) > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Rob Stryker > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3736: --------------------------------- Assignee: Denis Golovin (was: Fred Bricon) > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Denis Golovin > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3736: -------------------------------- > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3736: ------------------------------ Fix Version/s: 9.1.0.CR1 > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21947) Docker connection does not work after cdk restart

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21947?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21947: --------------------------------------- Apparently, vagrant-service-manager has been released (not sure when exactly, but it's available just using vagrant plugin update). And I verified that I cannot reproduce the original problem now (with 0.0.5 installed). So I could almost resolve this JIRA. But we need to make sure that cdk distribution is updated with this new version - I guess we check when a new version of CDK is available? > Docker connection does not work after cdk restart > ------------------------------------------------- > > Key: JBIDE-21947 > URL: https://issues.jboss.org/browse/JBIDE-21947 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Martin Malina > Assignee: Hardy Ferentschik > Fix For: 4.3.1.CR1 > > > When you set up cdk and start it for the first time, docker connection is properly set up and functioning. But when you restart cdk in the servers view, docker connection will no longer work. > This is caused by a bug in vagrant-service-manager 0.0.4: > https://github.com/projectatomic/vagrant-service-manager/issues/80 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3736) Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3736?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3736: ----------------------------------- the cdk changed the directory where the vagrantfile is stored (cdk/components/rhel/rhel-ose), our hard coded path (cdk/openshift-vagrant/) doesn't work anymore > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent > -------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3736 > URL: https://issues.jboss.org/browse/JBDS-3736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Fred Bricon > Fix For: 9.1.0.CR1 > > > Installer - When the user starts JBDS from the all-in-one installer, the detection of the CDK should be silent. The CDK, however, is reported to the user as a newly found runtime. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21997) Aeri causes NPE when running unittests

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21997?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-21997 at 3/30/16 11:58 AM: ----------------------------------------------------------------------- took the liberty to update description to describe the actual issue - fix is to update aeri TP was (Author: maxandersen): took the liberty to update description to describe the actual issue - fix is to update in aeri > Aeri causes NPE when running unittests > -------------------------------------- > > Key: JBIDE-21997 > URL: https://issues.jboss.org/browse/JBIDE-21997 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aeri, target-platform > Affects Versions: 4.3.1.CR1 > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.CR1 > > > an Eclipse bug was fixed 4 weeks ago in AERi and we need this fix to launch Integration tests for JBoss Fuse Tooling. > We need the version containing the fix of https://bugs.eclipse.org/bugs/show_bug.cgi?id=488868 > Seems that we need to use the org.eclipse.epp.logging.aeri.core_1.100.0.v20160304-1116.jar although we are using org.eclipse.epp.logging.aeri.core_1.100.0.v20160211-1103 > Please take care because the version number are both 1.100.0 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21829) Error when starting an OpenShift Server immediately after workspace startup

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21829. --------------------------------- Resolution: Done Verified on nightly build of JBT with OpenShift plugin build B257. > Error when starting an OpenShift Server immediately after workspace startup > --------------------------------------------------------------------------- > > Key: JBIDE-21829 > URL: https://issues.jboss.org/browse/JBIDE-21829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff Cantrill > Priority: Blocker > Fix For: 4.3.1.CR1 > > > I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter: > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597 > !MESSAGE An internal error occurred during: "Setting connection, deploy project...". > !STACK 0 > com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256) > at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This error also happens when the editor is closed at start-up and opened later on. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016