March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25772) java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25772?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25772: ------------------------------- Sprint: devex #146 March 2018 > java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio > ------------------------------------------------------------------------------------ > > Key: JBIDE-25772 > URL: https://issues.jboss.org/browse/JBIDE-25772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, runtime-detection, server > Affects Versions: 4.5.3.AM2 > Environment: DevStudio: 11.3.0.AM2-v20180301-2015-B2134 > CDK 3.3.0 > F27 > Reporter: Josef Kopriva > Assignee: Rob Stryker > Fix For: 4.5.3.AM3 > > > {code:java} > eclipse.buildId=11.3.0.AM2-v20180301-2015-B2134 > java.version=1.8.0_161 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Tue Mar 06 09:55:15 CET 2018 > An internal error occurred during: "Searching runtimes...". > java.lang.IllegalArgumentException: JSON parser error > at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1294) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.getHypervisor(CDK3RuntimeDetector.java:142) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.initializeServer(CDK3RuntimeDetector.java:123) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.AbstractCDKRuntimeDetector.initializeRuntime(AbstractCDKRuntimeDetector.java:59) > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:98) > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:56) > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 27+)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-23738. ------------------------------ Resolution: Won't Do Won't do. If anyone wants this, please vote loudly for it. > create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 27+) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23738 > URL: https://issues.jboss.org/browse/JBIDE-23738 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, rpm > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.6.x > > > Per trello card [1], we should consider having a jbosstools rpm. > Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies. > [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25772) java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25772?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25772: ------------------------------- Fix Version/s: 4.5.3.AM3 > java.lang.IllegalArgumentException: JSON parser error after first start of DevStudio > ------------------------------------------------------------------------------------ > > Key: JBIDE-25772 > URL: https://issues.jboss.org/browse/JBIDE-25772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift, runtime-detection, server > Affects Versions: 4.5.3.AM2 > Environment: DevStudio: 11.3.0.AM2-v20180301-2015-B2134 > CDK 3.3.0 > F27 > Reporter: Josef Kopriva > Fix For: 4.5.3.AM3 > > > {code:java} > eclipse.buildId=11.3.0.AM2-v20180301-2015-B2134 > java.version=1.8.0_161 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.eclipse.core.jobs > Error > Tue Mar 06 09:55:15 CET 2018 > An internal error occurred during: "Searching runtimes...". > java.lang.IllegalArgumentException: JSON parser error > at org.jboss.dmr.ModelNode.fromJSONString(ModelNode.java:1294) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.getHypervisor(CDK3RuntimeDetector.java:142) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDK3RuntimeDetector.initializeServer(CDK3RuntimeDetector.java:123) > at org.jboss.tools.openshift.cdk.server.core.internal.detection.AbstractCDKRuntimeDetector.initializeRuntime(AbstractCDKRuntimeDetector.java:59) > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:98) > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:56) > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-23738) create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 27+)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23738?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23738: ------------------------------- Fix Version/s: 4.5.3.Final (was: 4.6.x) > create jbosstools rpm that only depends on eclipse-* bundles (and can run on Fedora 27+) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23738 > URL: https://issues.jboss.org/browse/JBIDE-23738 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, rpm > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.3.Final > > > Per trello card [1], we should consider having a jbosstools rpm. > Could put the source for this in https://github.com/jbosstools/jbosstools-build-sites/tree/master/aggregate/ or in jbdevstudio-product since it'll be a similar design to that one, including blacklists and dependencies. > [1] https://trello.com/c/YK6rdGRy/14-create-jbosstools-rpm-for-fedora-24-25 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-24445) OpenShift server adapter is not working, when rsync is not on path (Upstream issue)

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24445?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24445: --------------------------------------- I think this issue could be closed, because I was not able to reproduce this and the upstream issue is also closed. WDYT: [~dbocharov] [~jeffmaury] [~adietish] ? > OpenShift server adapter is not working, when rsync is not on path (Upstream issue) > ----------------------------------------------------------------------------------- > > Key: JBIDE-24445 > URL: https://issues.jboss.org/browse/JBIDE-24445 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.4.Final > Environment: Windows 10 > Reporter: Radim Hopp > Labels: openshift_v3, server_adapter > Fix For: 4.5.x > > > Using server adapter, when rsync is not on path results in errors like: > {noformat} > Could not sync C:\Users\jbossqa\rhopp\workspace-sidnfiweun\.metadata\.plugins\org.jboss.ide.eclipse.as.core\dfgdfg@eap-app\deploy to all pods running the service eap-app > OpenShiftBinaryCapability process exited: WARNING: rsync command not found in path. Download cwRsync for Windows and add it to your PATH. > Ignoring the following flags because they only apply to rsync: --exclude > tar: ROOT.war/META-INF/MANIFEST.MF: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.properties: Cannot open: Not a directory > tar: ROOT.war/META-INF/maven/org.jboss.quickstarts.eap/jboss-kitchensink/pom.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/beans.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/META-INF/persistence.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/import.sql: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/controller/MemberController.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberListProducer.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/data/MemberRepository.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/model/Member.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/JaxRsActivator.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/rest/MemberResourceRESTService.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/service/MemberRegistration.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/classes/org/jboss/as/quickstarts/kitchensink/util/Resources.class: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/faces-config.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/kitchensink-quickstart-ds.xml: Cannot open: Not a directory > tar: ROOT.war/WEB-INF/templates/default.xhtml: Cannot open: Not a directory > tar: ROOT.war/index.html: Cannot open: Not a directory > tar: ROOT.war/index.xhtml: Cannot open: Not a directory > tar: ROOT.war/resources/css/screen.css: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/asidebkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/banner.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/bkg-blkheader.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/headerbkg.png: Cannot open: Not a directory > tar: ROOT.war/resources/gfx/rhjb_eap_logo.png: Cannot open: Not a directory > tar: Exiting with failure status due to previous errors > error: error extracting tar at destination directory: command terminated with exit code 2 > {noformat} > More info in upstream issue: https://github.com/openshift/origin/issues/14075 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-532?page=com.atlassian.jira.plugin.sy... ] Nick Boldt closed ERT-532. -------------------------- Resolution: Done > Overall repo merge issue [EBZ#525342] > ------------------------------------- > > Key: ERT-532 > URL: https://issues.jboss.org/browse/ERT-532 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) M6 > > > Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: > * common > * servertools > * sourceediting > * jsdt > * javaee-ejb > * webservices > * jsf > * dali > [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... > First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 > Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-533) enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-533?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-533: --------------------------- Sprint: devex #142 December 2017, devex #146 March 2018 (was: devex #142 December 2017) > enable use of tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata to ensure correct plugin and feature versioning between releases [EBZ#527533] > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: ERT-533 > URL: https://issues.jboss.org/browse/ERT-533 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) > > > As mentioned on https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg10522.html WTP uses some sort of versioncheck magic to ensure plugins and features are bumped appropriately. > We might want to switch to use the tycho-p2-extras-plugin:compare-version-with-baselines and tycho-p2-plugin:attached-p2-metadata mojos to ensure correct plugin and feature versioning, by settings stable and staging URLs as baselines. > For this to work, we need two things: > a) all components must build with Tycho 1.0 > b) a staging and stable URL must be provided against which to compare versions. > The staging site could be the latest I build or else a committers build, such as one of these, built via the current wtp.releng.aggretor build: > * http://download.eclipse.org/webtools/downloads/drops/R3.10.0/I-3.10.0-201... > * http://build.eclipse.org/webtools/committers/wtp-R3.10.0-I/20171030195222... > It should ultimately be a composite or aggregate site built from the collection of WTP subproject builds. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25127) [upstream] Work to improve webtools releng

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25127?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25127: ------------------------------- Sprint: devex #139 October 2017, devex #142 December 2017, devex #145 February 2018, devex #146 March 2018 (was: devex #139 October 2017, devex #142 December 2017, devex #145 February 2018) > [upstream] Work to improve webtools releng > ------------------------------------------ > > Key: JBIDE-25127 > URL: https://issues.jboss.org/browse/JBIDE-25127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > > Epic to track work done upstream at Eclipse for webtools project -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25771) Update Docker Tooling to 3.2.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25771?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25771: ------------------------------- Sprint: devex #146 March 2018 > Update Docker Tooling to 3.2.1 > ------------------------------ > > Key: JBIDE-25771 > URL: https://issues.jboss.org/browse/JBIDE-25771 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Affects Versions: 4.5.3.AM2 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 4.5.3.AM3 > > > Please update Docker Tooling to latest version to include this patch: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=531883 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-25598) TP: update target platform & Central to Oxygen.3a

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25598?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25598: ------------------------------- Sprint: devex #145 February 2018, devex #146 March 2018 (was: devex #145 February 2018) > TP: update target platform & Central to Oxygen.3a > ------------------------------------------------- > > Key: JBIDE-25598 > URL: https://issues.jboss.org/browse/JBIDE-25598 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.5.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.3.AM3, 4.5.3.Final > > > Switch to the latest Oxygen.3. Bits will be available starting in 4.5.3.AM2 sprint but won't be GA until 4.5.3.AM3 sprint. Then we'll move up to Oxygen.3a for the Final/GA sprint. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 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 2018