September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-20431) Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20431?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20431: ------------------------------- Summary: Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features (was: Make sure all installed features are shown in Help->About->Installation Details->Features) > Make sure all installed features have branding features and are shown in Help->About->Installation Details->Features > -------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20431 > URL: https://issues.jboss.org/browse/JBIDE-20431 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, common, visual-page-editor-core > Affects Versions: 4.3.0.Beta2 > Reporter: Alexey Kazakov > Assignee: Jeff MAURY > Fix For: 4.5.x > > > We miss a few features in Help->About->Installation Details->Features such as VPE, browsersim, JST. Maybe more. > See JBIDE-20069 for details how we can fix that. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24948) Update RedDeer in TP to 2.0.0.Beta

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24948?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24948: ------------------------------------ New PR: Replaced by https://github.com/jbosstools/jbosstools-target-platforms/pull/274 > Update RedDeer in TP to 2.0.0.Beta > ---------------------------------- > > Key: JBIDE-24948 > URL: https://issues.jboss.org/browse/JBIDE-24948 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.1.AM1 > Reporter: Rastislav Wagner > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.1.AM2 > > > We would like to update reddeer in TP to 2.0.0.Beta. Update site at eclipse is here http://download.eclipse.org/reddeer/milestones/2.0.0.Beta/ > Im not sure which job at CCI I should use to mirror the eclipse site so I will leave it for you [~nickboldt] . -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24937) update target platform to include docker tools from Linux Tools 6.1.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24937?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24937: ------------------------------------ New docker tools mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/docker/3.1.1.20... > update target platform to include docker tools from Linux Tools 6.1.1 > --------------------------------------------------------------------- > > Key: JBIDE-24937 > URL: https://issues.jboss.org/browse/JBIDE-24937 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: docker, target-platform > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Once [~jjohnstn] has it ready, update the target platform to include the latest Docker and Vagrant tools. ETA Sep 7 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24966) linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24966?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24966: ------------------------------------ New docker tools mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/docker/3.1.1.20... > linuxtools.reddeer should depend on eclipse.reddeer 2.0, not jboss.reddeer 1.2 > ------------------------------------------------------------------------------ > > Key: JBIDE-24966 > URL: https://issues.jboss.org/browse/JBIDE-24966 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, docker, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.5.1.AM2 > > > Turns out we have a blocker here. > org.eclipse.linuxtools.docker.reddeer depends on the old namespace org.jboss.reddeer.* plugins, but the plan for JBoss Tools 4.5.1 is to move to Red Deer 2.0, which has migrated to the org.eclipse.reddeer namespace. > Therefore this manifest needs to be changed, if we want to include Red Deer 2.0 in jbosstools 4.5.1.AM2 / devstudio 11.1.0.AM2: > {code:title=org.eclipse.linuxtools.docker.reddeer_1.0.0.201708220400.jar/META-INF/MANIFEST.MF} > Require-Bundle: org.junit,org.eclipse.swt, > org.eclipse.ui, > org.eclipse.osgi,org.eclipse.core.runtime, > org.jboss.reddeer.eclipse;bundle-version="1.2.1", << > org.jboss.reddeer.common;bundle-version="1.2.1", << > org.jboss.reddeer.swt;bundle-version="1.2.1", << > org.jboss.reddeer.core;bundle-version="1.2.1", << > org.jboss.reddeer.workbench;bundle-version="1.2.1", << > org.apache.commons.lang;bundle-version="2.6.0", > org.eclipse.linuxtools.docker.core, > org.hamcrest.library;bundle-version="1.3.0", > org.hamcrest.core;bundle-version="1.3.0"{code} > Note that the target platform freeze for the upcoming AM2 milestone is next Tuesday, Sept 12. Ideally, this would be fixed a few days before, so that I can apply other changes in advance. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24987) fix TP PR jobs so they run p2diff against last available published TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24987?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24987: ------------------------------- Fix Version/s: 4.5.1.AM2 > fix TP PR jobs so they run p2diff against last available published TP > --------------------------------------------------------------------- > > Key: JBIDE-24987 > URL: https://issues.jboss.org/browse/JBIDE-24987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Fix For: 4.5.1.AM2 > > > Realized today that the TP PR job is failing because it's trying to diff against a TP URL that doesn't (yet) exist. > So, pass in these params: > {code}-DtargetRepositoryURL=\ > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/${T... \ > -Dp2diff.skip=false{code} > If this doesn't work we can just skip the p2diff check entirely. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24987) fix TP PR jobs so they run p2diff against last available published TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24987?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24987: ---------------------------------- Assignee: Nick Boldt > fix TP PR jobs so they run p2diff against last available published TP > --------------------------------------------------------------------- > > Key: JBIDE-24987 > URL: https://issues.jboss.org/browse/JBIDE-24987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Realized today that the TP PR job is failing because it's trying to diff against a TP URL that doesn't (yet) exist. > So, pass in these params: > {code}-DtargetRepositoryURL=\ > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/${T... \ > -Dp2diff.skip=false{code} > If this doesn't work we can just skip the p2diff check entirely. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24987) fix TP PR jobs so they run p2diff against last available published TP

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24987?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24987: ------------------------------------ Using the same commadline invocation as the TP builds themselves [1], the PR job fails [2] to run the p2diff app: {code} !SESSION 2017-09-06 16:31:17.196 ----------------------------------------------- eclipse.buildId=unknown java.version=1.8.0_131 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments: -application org.eclipse.equinox.p2.example.p2diff.application -outputFile=/mnt/hudson_workspace/workspace/jbosstoolstargetplatform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff -mode=ignoreVersions file:///mnt/hudson_workspace/workspace/jbosstoolstargetplatform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... Command-line arguments: -consolelog -debug -clean -application org.eclipse.equinox.p2.example.p2diff.application -outputFile=/mnt/hudson_workspace/workspace/jbosstoolstargetplatform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple-ignoreVersions.p2diff -mode=ignoreVersions file:///mnt/hudson_workspace/workspace/jbosstoolstargetplatform-Pull-Request/jbosstools/multiple/target/jbosstools-multiple.target.repo http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7... !ENTRY org.eclipse.osgi 4 0 2017-09-06 16:31:22.950 !MESSAGE Application error !STACK 1 java.io.IOException: No such file or directory at java.io.UnixFileSystem.createFileExclusively(Native Method) at java.io.File.createNewFile(File.java:1012) at org.eclipse.equinox.p2.example.p2diff.Application.start(Application.java:50) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) at org.eclipse.equinox.launcher.Main.run(Main.java:1515) at org.eclipse.equinox.launcher.Main.main(Main.java:1488){code} [1] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... [2] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... So, screw it, I'm disabling the p2diff check unless anyone has a better idea? > fix TP PR jobs so they run p2diff against last available published TP > --------------------------------------------------------------------- > > Key: JBIDE-24987 > URL: https://issues.jboss.org/browse/JBIDE-24987 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > > Realized today that the TP PR job is failing because it's trying to diff against a TP URL that doesn't (yet) exist. > So, pass in these params: > {code}-DtargetRepositoryURL=\ > http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/${T... \ > -Dp2diff.skip=false{code} > If this doesn't work we can just skip the p2diff check entirely. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) Refactoring: eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Description: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * *MERGED* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * *DONE* refactoring as per JBDS-3894 * *DONE* documentation as per JBIDE-23510 was: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * *MERGED* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... * *DONE* refactoring as per JBDS-3894 * documentation as per JBIDE-23510 > Refactoring: eliminate devstudio target platform; reuse jbosstools target platform > ---------------------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM2 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-4440 - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * *MERGED* jbosstools-discovery repo - remove unneeded configuration / folders: https://github.com/jbosstools/jbosstools-target-platforms/pull/272 > * *DONE* job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * *DONE* job(s) / release guide steps that rename/copy target platforms to staging - change source of TPs to copy/rename to reuse the jbosstools artifacts: https://github.com/jbdevstudio/jbdevstudio-ci/commit/1eae61df0584de84adbb... > * *DONE* jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one: JBDS-4440 - https://github.com/jbdevstudio/jbdevstudio-product/commit/abf303e1e9ecff4... > * *DONE* refactoring as per JBDS-3894 > * *DONE* documentation as per JBIDE-23510 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-523) Running C/C++ applications on remote Docker daemon is not working [EBZ#520536]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-523?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-523. ------------------------------- Fix Version/s: Oxygen.1 (4.7) (was: Oxygen.2 (4.7)) Resolution: Done Labels: 6.1.1 Docker bzira (was: 6.2.0 Docker bzira) > Running C/C++ applications on remote Docker daemon is not working [EBZ#520536] > ------------------------------------------------------------------------------ > > Key: ERT-523 > URL: https://issues.jboss.org/browse/ERT-523 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: Docker, bzira, 6.1.1 > Fix For: Oxygen.1 (4.7) > > > The new 6.1.0 release of Linux Tools no longer supports running C/C++ applications on a remote Docker daemon. A local daemon continues to work, but not the remote one. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-525) Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-525?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-525. ------------------------------- Fix Version/s: Oxygen.1 (4.7) Assignee: Jeff Johnston Resolution: Done > Docker launch not able to handle debugging C/C++ programs that printf without newlines [EBZ#521211] > --------------------------------------------------------------------------------------------------- > > Key: ERT-525 > URL: https://issues.jboss.org/browse/ERT-525 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 6.1.1, Docker, bzira > Fix For: Oxygen.1 (4.7) > > > Using the CDT Debug in Container support for C/C++ applications, if a simple C application does a printf without a newline, the line may or may not be shown while stepping or running the program inside gdbserver. It appears that the Docker daemon is not reliable in delivering output in such a case and sometimes it turns up too late (e.g. gdbserver and the application are both finished) so it does not appear. Sometimes it shows up after gdbserver and the application is finished. In such a case, a line containing a single LineFeed character is printed in the place it should have been printed in the first place. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 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 September 2017