June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22178) [thym] Installed plugins don't show up in Config Editor UI

by Angel Misevski (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22178?page=com.atlassian.jira.plugi... ] Angel Misevski updated JBIDE-22178: ----------------------------------- Fix Version/s: (was: 4.4.x) > [thym] Installed plugins don't show up in Config Editor UI > ---------------------------------------------------------- > > Key: JBIDE-22178 > URL: https://issues.jboss.org/browse/JBIDE-22178 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Angel Misevski > Fix For: 4.4.1.Alpha1 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=491757 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22582) prepare to release install-grinder 4.4.0.Final

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22582?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-22582. ------------------------------------ Assignee: Alexey Kazakov (was: Mickael Istria) Resolution: Done We do not need a branching model a-la jbosstools-whateverComponent for install-grinder because it's always backward compatible. So having a master + some tags for some specific versions is enough. This issue of missing parent will keep on happening while we do not release any root parent pom. Anyway, it seems like [~akazakov] did change the version of parent pom for install-grinder, so let's mark this as done. > prepare to release install-grinder 4.4.0.Final > ---------------------------------------------- > > Key: JBIDE-22582 > URL: https://issues.jboss.org/browse/JBIDE-22582 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: install-tests > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.0.Final > > > Today I realized that there was no 4.4.0.x branch for install grinder, and it's still using parent pom 4.4.0.Alpha1. > [~akazakov] created the 4.4.0.x branch, and switched the root pom to use parent pom 4.4.0.Final-SNAPSHOT, but in doing so the project won't build because child poms are looking for root pom versioned 4.4.0.Alpha1, not 4.4.0.Final. > So... that needs to be fixed. But we should also release install grinder next week to Nexus as version 4.4.0.Final. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22587) install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22587?page=com.atlassian.jira.plugi... ] Mickael Istria closed JBIDE-22587. ---------------------------------- Resolution: Rejected I'm rejecting this jira as invalid. Feel free to open an enhancement request against "base" component to have the properties resolver a bit more verbose. > install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url > ----------------------------------------------------------------------------------- > > Key: JBIDE-22587 > URL: https://issues.jboss.org/browse/JBIDE-22587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Final > > > {code} > 10:05:00 [2016-06-10T10-5-0] Status ERROR: org.eclipse.mylyn.discovery.core code=0 org.jboss.tools.central.discovery_4.4.0.Final_v20160610_0958_B5.jar_2268305561361558535.jar: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}" org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}", Exception: > 10:05:00 org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}"{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ] Len DiMaggio commented on JBIDE-22604: -------------------------------------- Manual vagrant up works fine with RC2,RC3 and RC4 (with folder sync using vagrant-sshfs). But the issue comes only with devstudio and platform installer where Java program is performing the vagrant up. > CDK server adapter stuck at starting > ------------------------------------ > > Key: JBIDE-22604 > URL: https://issues.jboss.org/browse/JBIDE-22604 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.0.Final > Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe > devstudio 10.0.0.GA-a > CDK 2.1.RC3 > Reporter: Jan Richter > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.4.0.Final > > > I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'. > In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout. > Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-22609: ------------------------------------ That wrong IP address is returned by vagrant service-manager, when the provisioning was not complete. This could be seen on the two terminals in this screenshot: http://i.imgur.com/cmcBvDy.png > Provided wrong credentials, CDK server adapter says "started" even though it is not. > ------------------------------------------------------------------------------------ > > Key: JBIDE-22609 > URL: https://issues.jboss.org/browse/JBIDE-22609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10 > Reporter: Radim Hopp > Priority: Critical > > When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21099) ModelUiPreferencesPageTest.testEditorsPreferencesPage failure

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21099?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21099. --------------------------------- jbosstools-base_master is blue in jenkins. Closing. > ModelUiPreferencesPageTest.testEditorsPreferencesPage failure > ------------------------------------------------------------- > > Key: JBIDE-21099 > URL: https://issues.jboss.org/browse/JBIDE-21099 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > Failed tests: > ModelUiPreferencesPageTest.testEditorsPreferencesPage:53->PreferencePageTest.doDefaultTest:49 Selected page is not an instance of PreferencePage -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21716) Don't re-prompt for password

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21716?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21716. --------------------------------- [~jrichter1] confirmed for me that he is not prompted for password again when launching cdk after installing devsuite. [~rhopp] confirms also. Closing. > Don't re-prompt for password > ---------------------------- > > Key: JBIDE-21716 > URL: https://issues.jboss.org/browse/JBIDE-21716 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Reporter: Pete Muir > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > Having installed JBDS and CDK from the installer, and entered your password there, you get re-prompted for your password for the customer portal. This is a poor user experience. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22609) Provided wrong credentials, CDK server adapter says "started" even though it is not.

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22609?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22609: --------------------------------------- At first I couldn't reproduce this - I had a box that I previously started with the correct credentials. So to reproduce it's important that you do vagrant destroy first. With that I can reproduce this easily. > Provided wrong credentials, CDK server adapter says "started" even though it is not. > ------------------------------------------------------------------------------------ > > Key: JBIDE-22609 > URL: https://issues.jboss.org/browse/JBIDE-22609 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.0.Final > Environment: Devstudio 10.0.0.GA (B33), CDK 2.1.RC4, Windows 10 > Reporter: Radim Hopp > Priority: Critical > > When CDK startup fails when it is provided wrong credentials (it fails on vagrant-registration), CDK server adapter sets its state to "started" and OS3 connection is created (even though OS3 is not running in vagrant) with some weird IP (10.0.2.15). Also error pops up saying "The CDK VM is up and running, but OpenShift is unreachable at url https://10.0.2.15:8443/healthz/ready". I really don't know where this IP comes from. I was able to reproduce it on Fedora using libvirt box and the IP was something like (192.168.x.x) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3953) JBoss Studio Developer crash at startup on Fedora 24

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3953?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3953: --------------------------------- Component/s: upstream > JBoss Studio Developer crash at startup on Fedora 24 > ---------------------------------------------------- > > Key: JBDS-3953 > URL: https://issues.jboss.org/browse/JBDS-3953 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.GA > Environment: Fedora 24 > openjdk full version "1.8.0_92-b14" > Reporter: Donato Marrazzo > Priority: Blocker > Attachments: hs_err_pid12689.log > > > After installation, as I launch JBS, it just display the eclipse workbench for few second that it crash. > Despite the console message, no core dump is generated. > This is the cmd line output: > SLF4J: Class path contains multiple SLF4J bindings. > SLF4J: Found binding in [bundleresource://1072.fwk923366543:1/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: Found binding in [bundleresource://1072.fwk923366543:2/org/slf4j/impl/StaticLoggerBinder.class] > SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an explanation. > SLF4J: Actual binding is of type [ch.qos.logback.classic.util.ContextSelectorStaticBinder] > 14:09:55.604 [Worker-2] DEBUG o.e.m.c.i.p.r.ProjectRegistryRefreshJob - Queued refresh request: [/RemoteSystemsTempFiles/pom.xml] > openjdk version "1.8.0_92" > OpenJDK Runtime Environment (build 1.8.0_92-b14) > OpenJDK 64-Bit Server VM (build 25.92-b14, mixed mode) > 14:09:57.115 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.142 [Worker-14] DEBUG o.e.a.i.i.DefaultLocalRepositoryProvider - Using manager EnhancedLocalRepositoryManager with priority 10.0 for /home/donato/.m2/repository > 14:09:57.143 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshing: [L/RemoteSystemsTempFiles/pom.xml] > 14:09:57.156 [Worker-14] DEBUG o.e.m.c.i.p.r.ProjectRegistryManager - Refreshed: [L/RemoteSystemsTempFiles/pom.xml] > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x00007f521a6d7bfe, pid=12689, tid=0x00007f52cf5a3700 > # > # JRE version: OpenJDK Runtime Environment (8.0_92-b14) (build 1.8.0_92-b14) > # Java VM: OpenJDK 64-Bit Server VM (25.92-b14 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [libjavascriptcoregtk-3.0.so.0+0x4d4bfe] JSC::VM::throwException(JSC::ExecState*, JSC::JSValue)+0x236e > # > # Core dump written. Default location: /home/donato/core or core.12689 > # > # An error report file with more information is saved as: > # /home/donato/hs_err_pid12689.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.java.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20971) Knowledge Base validation preference is ignored

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20971?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20971. --------------------------------- Verified in devstudio 10.0.0.GA B33. After I disable KB validation in the global preferences, the projects are rebuilt and the warning disappears from the Problems view. > Knowledge Base validation preference is ignored > ----------------------------------------------- > > Key: JBIDE-20971 > URL: https://issues.jboss.org/browse/JBIDE-20971 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common/jst/core > Affects Versions: 4.3.0.CR2 > Reporter: Alexey Kazakov > Assignee: Viacheslav Kabanovich > Fix For: 4.4.0.Alpha1 > > > 1. Create two java project, Project1 and Project2 > 2. Project1 depends on Project2 > 3. Enable KB support for Project1 (Proejct Properties->JBoss Tools Knowledge Base) > 4. ASSERT: There is a warning on Project1 that there is no KB nature installed on required Projet2. > 5. Go to Preferences->JBoss Tools->Web->Knowledge Base->Validator > 6. Uncheck Enable Validation > 7. Clean/rebuild Project1 > 8. FAILURE: The warning is still there > If you set "Capabilities are not enabled in Java uitl module" to "Ignore" then the warning disappears. > It looks like when we disable the KB validator at all then the old warning is not removed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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