October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-929) Fuse project starter is available in Central only if we check EarlyAccess

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBTIS-929?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBTIS-929: ----------------------------------- Actually the problem is most likely caused by the aforementioned fix not being available to JBDS 9 (see https://github.com/jbosstools/jbosstools-central-webpage/commit/7b6913ed4... and https://github.com/jbosstools/jbosstools-central-webpage/commit/c3bc9380b...) It's unlikely we can backport the commits as-is into the JBDS 9 stream, as some changes are required on the java side. But we may be able to simply always enable fuse if it's no longer in EA in 9.x. Can someone confirm? > Fuse project starter is available in Central only if we check EarlyAccess > ------------------------------------------------------------------------- > > Key: JBTIS-929 > URL: https://issues.jboss.org/browse/JBTIS-929 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution, Fuse IDE > Affects Versions: 9.0.2.GA > Environment: JBDS 9.1.0.GA + JBDS-IS 9.0.2.GA > Reporter: Andrej Podhradsky > > Fuse project starter is available in Central only if we check EarlyAccess. Moreover, if you close and reopen the RedHat Central then the project starter dissappears. You have to uncheck and check the EA again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23363) Include Docker tooling source plugins/features in nightly site so they can be included downstream

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23363?page=com.atlassian.jira.plugi... ] Jeff Johnston resolved JBIDE-23363. ----------------------------------- Fix Version/s: 4.4.2.Final Resolution: Done > Include Docker tooling source plugins/features in nightly site so they can be included downstream > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23363 > URL: https://issues.jboss.org/browse/JBIDE-23363 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Fix For: 4.4.2.Final > > > The 4.60 and 4.61 TP do not have the source artifacts for Docker Tooling. They are not in http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23363) Include Docker tooling source plugins/features in nightly site so they can be included downstream

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23363?page=com.atlassian.jira.plugi... ] Jeff Johnston commented on JBIDE-23363: --------------------------------------- I have opened and resolved https://bugs.eclipse.org/bugs/show_bug.cgi?id=506007 Sources won't appear in non-nightly builds until the next Oxygen milestone. They will appear in the next nightly build which should occur this evening (Oct 14). > Include Docker tooling source plugins/features in nightly site so they can be included downstream > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23363 > URL: https://issues.jboss.org/browse/JBIDE-23363 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, upstream > Affects Versions: 4.4.2.AM2 > Reporter: Jeff MAURY > Assignee: Jeff Johnston > > The 4.60 and 4.61 TP do not have the source artifacts for Docker Tooling. They are not in http://download.jboss.org/jbosstools/updates/requirements/neon/201609281000 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3984) RHSCL/devstudio alignment tasks

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3984?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3984: ----------------------------- Fix Version/s: 10.2.0.GA (was: 10.2.0.AM2) > RHSCL/devstudio alignment tasks > ------------------------------- > > Key: JBDS-3984 > URL: https://issues.jboss.org/browse/JBDS-3984 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: build > Affects Versions: 10.1.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.GA > > > https://issues.jboss.org/browse/JBDS-3982 > https://issues.jboss.org/browse/JBDS-3981 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23360) Remember selected route in ambiguous routing does not work

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23360?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-23360: ----------------------------------------------- [~adietish], please take a look at the proposed solution. > Remember selected route in ambiguous routing does not work > ---------------------------------------------------------- > > Key: JBIDE-23360 > URL: https://issues.jboss.org/browse/JBIDE-23360 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: openshift_v3 > > When selecting Show In - Web Browser on a project with more services, routing is ambiguous. There is shown a shell "Select Route" with a checkbox "Remember selected route". This checkbox does not work. If I check it and then click OK button, I get the same prompt again next time I select Show In - Web Browser context menu item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4077: ---------------------------------- As noted in JBDS-4117, I've got these two jobs running, so we can compare the test results for 10.1.0.GA va. 10.2.0.latest: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst... > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Nick Boldt > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4117) integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4117?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4117: ---------------------------------- Running: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Inst... > integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4117 > URL: https://issues.jboss.org/browse/JBDS-4117 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, install-tests, integration-tests > Affects Versions: 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > integration tests job should fetch a copy of devstudio and install it headlessly, then pass that install folder to the maven test run process -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4059 at 10/14/16 1:20 PM: ------------------------------------------------------------ Regarding the issue of VPE/XulRunner/GTK2: [~maxandersen] said: {quote}Here is my suggestion: * List the features that are non-supportable on Red Hat Linux desktop. * Exclude or disable them by default in the RPM distro. * Document it and review it for the next years major release train as a team and with PM being aware of the issues. {quote} So, we should remove xulrunner and remove/disable whatever in devstudio depends on that, as it won't work in a GTK3 environment anyway. I'll prepare a PR for this. cc: [~ibuziuk] [~akazakov] [~akurtako] [~tim.moran] [~tmancini] [~rkratky] was (Author: nickboldt): Regarding the issue of VPE/XulRunner/GTK2: [~maxandersen] said: {quote}Here is my suggestion: * List the features that are non-supportable on Red Hat Linux desktop. * Exclude or disable them by default in the RPM distro. * Document it and review it for the next years major release train as a team and with PM being aware of the issues. {code} So, we should remove xulrunner and remove/disable whatever in devstudio depends on that, as it won't work in a GTK3 environment anyway. I'll prepare a PR for this. cc: [~ibuziuk] [~akazakov] [~akurtako] [~tim.moran] [~tmancini] [~rkratky] > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- Regarding the issue of VPE/XulRunner/GTK2: [~maxandersen] said: {quote}Here is my suggestion: * List the features that are non-supportable on Red Hat Linux desktop. * Exclude or disable them by default in the RPM distro. * Document it and review it for the next years major release train as a team and with PM being aware of the issues. {code} So, we should remove xulrunner and remove/disable whatever in devstudio depends on that, as it won't work in a GTK3 environment anyway. I'll prepare a PR for this. cc: [~ibuziuk] [~akazakov] [~akurtako] [~tim.moran] [~tmancini] [~rkratky] > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4096) profile self is not registered?

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4096?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4096: ----------------------------- Fix Version/s: 10.2.0.AM3 > profile self is not registered? > ------------------------------- > > Key: JBDS-4096 > URL: https://issues.jboss.org/browse/JBDS-4096 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central-update > Affects Versions: 10.2.0.AM1 > Environment: {code} > Red Hat JBoss Developer Studio > Version: 10.2.0.AM1 > Build id: AM1-v20160923-1714-B6096 > Build date: 20160923-1714 > $➔ uname -a > Linux t540p-f24-vm01 4.7.4-200.fc24.x86_64 #1 SMP Thu Sep 15 18:42:09 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > [14:00:12] nboldt@t540p-f24-vm01:~/devstudio-10.2.0.AM1 > $➔ java -version > openjdk version "1.8.0_65" > OpenJDK Runtime Environment (build 1.8.0_65-b17) > OpenJDK 64-Bit Server VM (build 25.65-b01, mixed mode) > {code} > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 10.2.0.AM3 > > Attachments: profile-self-is-not-registered.png > > > Tried to install the m2e-wtp-jsf connector from Central and got this: > {code}Profile id _SELF_ is not registered. > java.lang.IllegalArgumentException: Profile id _SELF_ is not registered. > at org.eclipse.equinox.internal.p2.director.ProfileChangeRequest.createByProfileId(ProfileChangeRequest.java:46) > at org.eclipse.equinox.p2.operations.InstallOperation.computeProfileChangeRequest(InstallOperation.java:74) > at org.eclipse.equinox.p2.operations.ProfileChangeOperation.makeResolveJob(ProfileChangeOperation.java:165) > at org.eclipse.equinox.p2.operations.ProfileChangeOperation.resolveModal(ProfileChangeOperation.java:113) > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.resolveInstall(PrepareInstallProfileJob.java:268) > at org.jboss.tools.discovery.core.internal.connectors.PrepareInstallProfileJob.run(PrepareInstallProfileJob.java:120) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > eclipse.buildId=unknown > java.version=1.8.0_65 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_CA > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product -debug -console -consolelog > {code} > !profile-self-is-not-registered.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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