February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4268) Problem installing JBoss OpenShift 3 Tools from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4268?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4268: ---------------------------------- Installed via RPM / droplet: {code} /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.openshift.cdk.feature_3.3.2.v20170213-2300 /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.openshift.egit.integration.feature_3.3.2.v20161213-1011 /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.openshift.express.feature_3.3.2.v20170206-2133 /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.openshift.feature_3.3.2.v20170214-0332 /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/features/org.jboss.tools.openshift.js.feature_3.3.2.v20170119-1710 /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.central_2.1.3.v20170116-1347/icons/openshift-logo-white-icon.png /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.cdk.server_3.3.2.v20170213-2300.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.client_3.3.2.Final-v20170214-0332-B1848.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.common.core_3.3.2.v20170206-2133.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.common.ui_3.3.2.v20170202-1544.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.core_3.3.2.v20170209-1118.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.egit.core_3.3.2.v20161213-1011.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.egit.ui_3.3.2.v20161213-1011.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.express.client_3.3.2.v20161213-1011.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.express.core_3.3.2.v20170119-1710.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.express.ui_3.3.2.v20170202-1544.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.js_3.3.2.v20170119-1710.jar /opt/rh/rh-eclipse46/root/usr/share/eclipse/droplets/devstudio/eclipse/plugins/org.jboss.tools.openshift.ui_3.3.2.v20170209-1534.jar {code} Installed from Central [1]: {code} ./features/org.jboss.tools.openshift.cdk.feature_3.3.2.v20170112-2250 ./features/org.jboss.tools.openshift.feature_3.3.2.v20170127-0820 ./plugins/org.jboss.tools.openshift.cdk.server_3.3.2.v20170112-2250.jar ./plugins/org.jboss.tools.openshift.client_3.3.2.AM2-v20170127-0820-B1805.jar ./plugins/org.jboss.tools.openshift.common.core_3.3.2.v20161213-1011.jar ./plugins/org.jboss.tools.openshift.common.ui_3.3.2.v20170105-1008.jar ./plugins/org.jboss.tools.openshift.core_3.3.2.v20170119-1710.jar ./plugins/org.jboss.tools.openshift.ui_3.3.2.v20170126-1430.jar {code} [1] https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.3.0.AM2-bui... I'm only getting errors related to openshift plugins now - nothing with m2e, docker, or jdt. [^rh-eclipse46-devstudio10.3-0.20170214.1451.el7.log.20170214-1203_strict.txt] So that's better... but not perfect. :D > Problem installing JBoss OpenShift 3 Tools from RH Central > ---------------------------------------------------------- > > Key: JBDS-4268 > URL: https://issues.jboss.org/browse/JBDS-4268 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: JBoss_OpenShift_3_Tools_from_central.png, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JBoss_OpenShift_3_Tools_from_central_strict.txt, rh-eclipse46-devstudio10.3-0.20170214.1451.el7.log.20170214-1203_strict.txt > > > The installation of JBoss OpenShift 3Tools from Red Hat Central causes problems during the start of eclipse. > These modules failed to start due to "Another singleton bundle selected": org.jboss.tools.openshift, org.eclipse.m2e, org.eclipse.linuxtools.docker, org.eclipse.jdt > Log: [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JBoss_OpenShift_3_Tools_from_central_strict.txt] > Features installed from RH Central: !JBoss_OpenShift_3_Tools_from_central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4268) Problem installing JBoss OpenShift 3 Tools from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4268?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4268: ----------------------------- Attachment: rh-eclipse46-devstudio10.3-0.20170214.1451.el7.log.20170214-1203_strict.txt > Problem installing JBoss OpenShift 3 Tools from RH Central > ---------------------------------------------------------- > > Key: JBDS-4268 > URL: https://issues.jboss.org/browse/JBDS-4268 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: JBoss_OpenShift_3_Tools_from_central.png, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JBoss_OpenShift_3_Tools_from_central_strict.txt, rh-eclipse46-devstudio10.3-0.20170214.1451.el7.log.20170214-1203_strict.txt > > > The installation of JBoss OpenShift 3Tools from Red Hat Central causes problems during the start of eclipse. > These modules failed to start due to "Another singleton bundle selected": org.jboss.tools.openshift, org.eclipse.m2e, org.eclipse.linuxtools.docker, org.eclipse.jdt > Log: [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JBoss_OpenShift_3_Tools_from_central_strict.txt] > Features installed from RH Central: !JBoss_OpenShift_3_Tools_from_central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4270) Problem installing JST Server from RH Central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4270?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4270: ---------------------------------- This is caused by the fact that the devstudio rpm installation now depends on the *webtools-servertools* droplet install (from rpm), and that is built in brew from tarball, so it can't see git and therefore can't reproduce qualifiers to match those in github. So, rpm-based builds of webtools-servertools contain apparently NEWER versions of the features/plugins that are included in the Central site. Eclipse should simply say "newer versions are installed" and prevent you from installing the old stuff. But it seems Eclipse does allow you to install OLD features on top of NEWER features, resulting in an install that contains both the old and new plugins. Here's what's in the RPM install (stuff from Neon.2, but with newer timestamps from 2017/01/27, not Dec 2016): {code} ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/features/org.eclipse.jst.server_adapters.ext.feature_3.3.501.v201701271400 ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/features/org.eclipse.jst.server_adapters.feature_3.2.400.v201701271400 ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/features/org.eclipse.jst.server_core.feature_3.4.300.v201701271400 ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/features/org.eclipse.jst.server_ui.feature_3.4.300.v201701271400 ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/features/org.eclipse.jst.server_userdoc.feature_3.3.300.v201701271400 ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.core_1.2.500.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.generic.core_1.0.900.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.generic.jonas_1.5.500.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.generic.ui_1.0.600.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.preview.adapter_1.1.300.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.tomcat.core_1.1.801.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.tomcat.ui_1.1.501.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.ui_1.1.300.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.ui.doc.user_1.0.600.v201701271400.jar ./rh-eclipse46/root/usr/share/eclipse/droplets/webtools-servertools/eclipse/plugins/org.eclipse.jst.server.ui.infopop_1.0.500.v201701271400.jar {code} And here's what I installed from Central/Earlyaccess [1] into ~/.eclipse - stuff from Neon.2): {code} ./features/org.eclipse.jst.server_adapters.feature_3.2.400.v201606081655 ./features/org.eclipse.jst.server_core.feature_3.4.300.v201606081655 ./features/org.eclipse.jst.server_ui.feature_3.4.300.v201606081655 ./features/org.eclipse.jst.server_userdoc.feature_3.3.300.v201503102136 ./plugins/org.eclipse.jst.server.core_1.2.500.v201603031514.jar ./plugins/org.eclipse.jst.server.generic.core_1.0.900.v201606081655.jar ./plugins/org.eclipse.jst.server.generic.ui_1.0.600.v201402262303.jar ./plugins/org.eclipse.jst.server.preview.adapter_1.1.300.v201606081655.jar ./plugins/org.eclipse.jst.server.ui_1.1.300.v201309182039.jar ./plugins/org.eclipse.jst.server.ui.doc.user_1.0.600.v201309182117.jar ./plugins/org.eclipse.jst.server.ui.infopop_1.0.500.v201309182117.jar {code} [1] https://devstudio.redhat.com/10.0/staging/builds/devstudio-10.3.0.AM2-bui... > Problem installing JST Server from RH Central > --------------------------------------------- > > Key: JBDS-4270 > URL: https://issues.jboss.org/browse/JBDS-4270 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: JST_Server_from_central.png, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JST_Server_from_central_strict.txt > > > The installation of JST Server from Red Hat Central causes problems during the start of eclipse. > There are "Another singleton bundle selected" related to org.eclipse.jst.server. > Log: [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JST_Server_from_central_strict.txt] > Features installed from RH Central: > !JST_Server_from_central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23603: ------------------------------------ [~dbocharov] Not really happy with you patch/workaround as it seems to follow the hard route. However, I noticed the following: when a single class is modified, the .class file is sent through rsync with a .isdeploying file. Looking at the Wildfly doc, we should send a .dodeploy so I went to the pod and once the rsync was finished did a touch ROOT.war.dodeploy and I was then able to see the change. Seems that this .dodeploy is sent when the server is started but not for incremental updates. I looked at the code and did not see where it was set but need @rob.stryker WDYT ? > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23603) Server adapter: changes to eap are (published but) not visible unless in debug

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23603?page=com.atlassian.jira.plugi... ] Jeff MAURY edited comment on JBIDE-23603 at 2/14/17 11:03 AM: -------------------------------------------------------------- [~dbocharov] Not really happy with you patch/workaround as it seems to follow the hard route. However, I noticed the following: when a single class is modified, the .class file is sent through rsync with a .isdeploying file. Looking at the Wildfly doc, we should send a .dodeploy so I went to the pod and once the rsync was finished did a touch ROOT.war.dodeploy and I was then able to see the change. Seems that this .dodeploy is sent when the server is started but not for incremental updates. I looked at the code and did not see where it was set but need [~rob.stryker] WDYT ? was (Author: jeffmaury): [~dbocharov] Not really happy with you patch/workaround as it seems to follow the hard route. However, I noticed the following: when a single class is modified, the .class file is sent through rsync with a .isdeploying file. Looking at the Wildfly doc, we should send a .dodeploy so I went to the pod and once the rsync was finished did a touch ROOT.war.dodeploy and I was then able to see the change. Seems that this .dodeploy is sent when the server is started but not for incremental updates. I looked at the code and did not see where it was set but need @rob.stryker WDYT ? > Server adapter: changes to eap are (published but) not visible unless in debug > ------------------------------------------------------------------------------ > > Key: JBIDE-23603 > URL: https://issues.jboss.org/browse/JBIDE-23603 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22869: ---------------------------------- Assignee: Rob Stryker (was: Jeff MAURY) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22869: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22869: ---------------------------------- Assignee: Rob Stryker (was: Jeff MAURY) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-22869: ---------------------------------- Assignee: Jeff MAURY (was: Rob Stryker) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Jeff MAURY > Fix For: 4.4.3.Final > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-22172) create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22172?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22172: ------------------------------- Summary: create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too) (was: create automated install test for JBDS installer jar + all early access content in Central) > create automated install smoke tests for devstudio installer jar + all early access content in Central (and jbt/ds BYOE installs too) > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22172 > URL: https://issues.jboss.org/browse/JBIDE-22172 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, install-tests > Affects Versions: 4.3.1.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final > > > To better automate staging & release, we need a way to run a smoke test of a given installer jar, then to install all the GA & EA content in Central. > Steps to script: > a. wget installer jar > b. headless install (via -console or install.xml script) > c. install grinder or p2director install all the things in Central. > Also need to smoke test the BYOE cases. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017