April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21667) Make computing property names more conspicuous

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21667?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21667. --------------------------------- > Make computing property names more conspicuous > ---------------------------------------------- > > Key: JBIDE-21667 > URL: https://issues.jboss.org/browse/JBIDE-21667 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Jeff Cantrill > Labels: code_quality > Fix For: 4.4.0.Alpha1 > > > Created as follow up to JBIDE-21590. > Property names of resources are computed in two places. > - From kind of resource in ResourcesUIModel: > {code} > private static String getProperty(String kind) { > return StringUtils.pluralize(kind.toLowerCase()); > } > {code} > - From tab id in OpenShiftResourcePropertySection.setInput : > {code} > String property = org.apache.commons.lang.StringUtils.right(id, id.length() - id.lastIndexOf(".") - 1); > {code} > Maybe, there are more places that transform something to property name, I am not aware of them yet. But, imho, even if they are only 2 places and no other will appear, they are too much related to be separate and hidden in the depth of implementation. I suggest a utility that will encapsulate all manipulations with resource property names, (being in an internal package it may have public methods without getting into API), and describe in Java docs in details how it works. Tests for this utility may help to find early if some modification breaks consistency of related names. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M6 or M7 target platform

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22200: ---------------------------------------- {quote}M6 was released on 03/25. Why wasn't this raised a month ago?{quote} My mistake, I got confused in when this API got actually introduced. > Create and use Neon M6 or M7 target platform > -------------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22255) Number of alterated OpenShift 3 Server Adapter should start from 2 not 1

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22255?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22255: ----------------------------------------------- There can be different views on this point, but indeed, when for example I copy/paste a Java source in the same package I get suffix 2, not 1, in the "Name Conflict" dialog. Some years ago it was prefix "CopyOf". Though, since I change the name all the same, it does not matter much. > Number of alterated OpenShift 3 Server Adapter should start from 2 not 1 > ------------------------------------------------------------------------ > > Key: JBIDE-22255 > URL: https://issues.jboss.org/browse/JBIDE-22255 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha1 > Reporter: Marián Labuda > Priority: Minor > Labels: openshift_v3, ux > Fix For: 4.4.x > > > When I create a New OpenShift 3 Server Adapter with same details as already an existing one server adapter, new one has altered label in Server view by number in parentheses. This starts with number 1. > Example: > I am having an OS 3 Server Adapter with label "eap-app at OpenShift 3 (10.1.2.2)" then I create a new OS 3 Server Adapter with same details and I get "eap-app at OpenShift 3 (10.1.2.2) (1)", what I think is not correct, because it is already second. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M6 or M7 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22200: ------------------------------------ M6 was released on 03/25. Why wasn't this raised a month ago? > Create and use Neon M6 or M7 target platform > -------------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M6 or M7 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22200: ------------------------------- Description: Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386. https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... Story points: 21 (fibonacci) * jbt tp, * jbds tp, * central tp; * jbt-build-sites, * jbds site build; * update install/matrix jobs to use new Eclipse JEE/platform binary; * mailing list announcements was: Prepare TP to use Neon M6 bits, which will be available 04/29 to 05/06. Cloned from JBIDE-21386. https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... Story points: 21 (fibonacci) * jbt tp, * jbds tp, * central tp; * jbt-build-sites, * jbds site build; * update install/matrix jobs to use new Eclipse JEE/platform binary; * mailing list announcements > Create and use Neon M6 or M7 target platform > -------------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Prepare TP to use Neon M6 or M7 bits, which will be available 03/18 to 03/25 or 04/29 to 05/06. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22200) Create and use Neon M6 or M7 target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22200?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22200: ------------------------------- Summary: Create and use Neon M6 or M7 target platform (was: Create and use Neon M6 target platform) > Create and use Neon M6 or M7 target platform > -------------------------------------------- > > Key: JBIDE-22200 > URL: https://issues.jboss.org/browse/JBIDE-22200 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform, upstream > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > Prepare TP to use Neon M6 bits, which will be available 04/29 to 05/06. Cloned from JBIDE-21386. > https://wiki.eclipse.org/index.php?title=Neon/Simultaneous_Release_Plan#S... > Story points: 21 (fibonacci) > * jbt tp, > * jbds tp, > * central tp; > * jbt-build-sites, > * jbds site build; > * update install/matrix jobs to use new Eclipse JEE/platform binary; > * mailing list announcements -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21602) Sonar build for openshift is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21602?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21602 at 4/27/16 10:19 AM: -------------------------------------------------------------------- Current state for OpenShift is that sonar is now running but FindBugs is not able to parse java8 lambda syntax: {code} [INFO] [01:44:27.466] Compare to previous version (2015-01-14) [INFO] [01:44:27.651] Initializer FindbugsMavenInitializer... [INFO] [01:44:27.728] Initializer FindbugsMavenInitializer done: 77 ms [INFO] [01:44:27.728] Base dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core [INFO] [01:44:27.728] Working dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/sonar [INFO] [01:44:27.729] Source dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src [INFO] [01:44:27.729] Binary dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/classes [INFO] [01:44:27.729] Source encoding: UTF-8, default locale: en_US [INFO] [01:44:27.743] Sensor JavaSourceImporter... [INFO] [01:44:28.038] Sensor JavaSourceImporter done: 295 ms [INFO] [01:44:28.038] Sensor JavaSquidSensor... [INFO] [01:44:28.104] Java AST scan... [ERROR] [01:44:28.242] Unable to parse source file : /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src/org/jboss/tools/openshift/egit/core/EGitUtils.java [ERROR] [01:44:28.246] Parse error at line 1549 column 14 failed to match all of: INC DEC BANG TILDA PLUS MINUS LPAR LPAR LPOINT THIS SUPER TRUE FALSE NULL CHARACTER_LITERAL LITERAL FLOAT_LITERAL DOUBLE_LITERAL LONG_LITERAL INTEGER_LITERAL NEW ENUM BYTE SHORT CHAR INT LONG FLOAT DOUBLE BOOLEAN VOID 1539: if (ORIGIN.equals(o1.getName())) { 1540: return -1; 1541: } 1542: if (ORIGIN.equals(o2.getName())) { 1543: return 1; 1544: } 1545: return o1.getName().compareToIgnoreCase(o2.getName()); 1546: } 1547: }); 1548: return remoteConfigs.stream() 1549: .map(rc -> getFetchURI(rc)) ^ 1550: .filter(uri -> uri != null && uri.toString().startsWith("http")) 1551: .map(URIish::toString); 1552: } 1553: } 1554: {code} was (Author: adietish): Current state for OpenShift is that sonar is now running but FindBugs is not able to parse java8 lambda syntax: {code} [INFO] [01:44:27.466] Compare to previous version (2015-01-14) [INFO] [01:44:27.651] Initializer FindbugsMavenInitializer... [INFO] [01:44:27.728] Initializer FindbugsMavenInitializer done: 77 ms [INFO] [01:44:27.728] Base dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core [INFO] [01:44:27.728] Working dir: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/sonar [INFO] [01:44:27.729] Source dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src [INFO] [01:44:27.729] Binary dirs: /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/target/classes [INFO] [01:44:27.729] Source encoding: UTF-8, default locale: en_US [INFO] [01:44:27.743] Sensor JavaSourceImporter... [INFO] [01:44:28.038] Sensor JavaSourceImporter done: 295 ms [INFO] [01:44:28.038] Sensor JavaSquidSensor... [INFO] [01:44:28.104] Java AST scan... [ERROR] [01:44:28.242] Unable to parse source file : /mnt/hudson_workspace/workspace/jbosstools-openshift.sonar_master/sources/plugins/org.jboss.tools.openshift.egit.core/src/org/jboss/tools/openshift/egit/core/EGitUtils.java [ERROR] [01:44:28.246] Parse error at line 1549 column 14 failed to match all of: INC DEC BANG TILDA PLUS MINUS LPAR LPAR LPOINT THIS SUPER TRUE FALSE NULL CHARACTER_LITERAL LITERAL FLOAT_LITERAL DOUBLE_LITERAL LONG_LITERAL INTEGER_LITERAL NEW ENUM BYTE SHORT CHAR INT LONG FLOAT DOUBLE BOOLEAN VOID 1539: if (ORIGIN.equals(o1.getName())) { 1540: return -1; 1541: } 1542: if (ORIGIN.equals(o2.getName())) { 1543: return 1; 1544: } 1545: return o1.getName().compareToIgnoreCase(o2.getName()); 1546: } 1547: }); 1548: return remoteConfigs.stream() 1549: .map(rc -> getFetchURI(rc)) ^ 1550: .filter(uri -> uri != null && uri.toString().startsWith("http")) 1551: .map(URIish::toString); 1552: } 1553: } 1554: {cdoe} > Sonar build for openshift is failing > ------------------------------------ > > Key: JBIDE-21602 > URL: https://issues.jboss.org/browse/JBIDE-21602 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Mickael Istria > Fix For: 4.4.x > > Attachments: sonar-build-output.txt > > > Sonar for openshift is currently failing in our jenkins at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > I see it complaining in the build about an incompatible bytecode version: > {code} > Caused by: java.lang.UnsupportedClassVersionError: org/eclipse/tycho/core/p2/P2ArtifactRepositoryLayout : Unsupported major.minor version 51.0 > {code} > The full build output is attached [^sonar-build-output.txt] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16647) Allow to fully update application from central

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16647?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-16647: ------------------------------------ Is this a customer request? community request? "Because having only one way to do something in Eclipse is insufficient" request? > Allow to fully update application from central > ---------------------------------------------- > > Key: JBIDE-16647 > URL: https://issues.jboss.org/browse/JBIDE-16647 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central-update > Reporter: Mickael Istria > Priority: Minor > Fix For: 4.4.x > > > Software/Update tab should contain a more explicit way to update the whole application (same as "Check for Updates" menu). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3860: ---------------------------------- Also, you should NOT be seeing URL pings to https://devstudio.redhat.com/9.0/staging/ from a fresh JBDS 9.1 install -- /staging/ URLs were never part of a JBDS install so you must have added them manually somehow. Please confirm. > JBDS 9.1 not connecting to internet > ----------------------------------- > > Key: JBDS-3860 > URL: https://issues.jboss.org/browse/JBDS-3860 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 9.1.0.GA > Reporter: Nichola Moore > Assignee: Alexey Kazakov > Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt > > > I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23. > When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window. > The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window. > [1] JBDS9.1_bug.png > [2] JBDS9.1_whole_screen.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3860: ---------------------------------- Can you download and run the p2 browser tool, then open the URLs from your error log? I'd like to know if the problem is your network or JBDS itself. https://github.com/ifedorenko/p2-browser --> one quick maven build (or use the jnlp launcher) and you have a very useful tool for exploring p2 update sites. Also, from your error log you appear to be seeing JBDS IS 8 in your JBDS 9 install. Are you reusing an old workspace? {code}!MESSAGE Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_1414459278561037199.jar, com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2573611549793918768.jar{code} This error suggests that your JBDS install is corrupt somehow and it trying to reuse a cert or key from an old install, but doesn't have permission. {code} failed on java.security.ProviderException: java.security.KeyException. Retry attempt 0 started {code} Suggestions: a) reinstall JBDS into a NEW folder, then point it at a NEW workspace folder - DO NOT reuse a JBDS 8 workspace. b) if that doesn't work, consider deleting your ~/.eclipse folder to remove cached permissions/keys used by an old Eclipse / JBDS installation. > JBDS 9.1 not connecting to internet > ----------------------------------- > > Key: JBDS-3860 > URL: https://issues.jboss.org/browse/JBDS-3860 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Affects Versions: 9.1.0.GA > Reporter: Nichola Moore > Assignee: Alexey Kazakov > Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt > > > I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23. > When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window. > The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window. > [1] JBDS9.1_bug.png > [2] JBDS9.1_whole_screen.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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