March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19509) JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19509?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-19509: ---------------------------------- Assignee: Denis Golovin > JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19509 > URL: https://issues.jboss.org/browse/JBIDE-19509 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Reporter: Nick Boldt > Assignee: Denis Golovin > > JBDS headless install no longer works in Jenkins, so versionwatch is unable to diff 9.0.0.Alpha2 master builds w/ previous Alpha1 and 8.1.x builds. > I've repeated exactly what the versionwatch script does locally and it's fine w/ JDK 7 and 8, so it's not a config problem. > But in Jenkins, with VNC enabled (and when not) the headless install process repeatedly stalls out at step 2: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio.versionwatch_master/1892/console} > [ Starting automated installation ] > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/3) ] > [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Alpha2 (2/3) ] > [ Unpacking finished ] ... > {code} > But in the 8.1.luna branch, the job is fine: > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatch_8.0.luna/363/console} > +++ /qa/tools/opt/jdk1.6.0_last/bin/java -jar /qa/services/http/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/jboss-devstudio-8.1.0.GA-v20150324-2058-B454-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-8.1.0.GA.install.xml > [ Starting automated installation ] > [ Starting to unpack ] > [ Processing package: P2 Director Application (1/3) ] > [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA (2/3) ] > [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA Metadata Generation (3/3) ] > [ Unpacking finished ] > [ Creating shortcuts done. ] > [ Add shortcuts to uninstaller done. ] > [ Writing the uninstaller data ... ] > [ Automated installation done ]{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19509) JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-19509: ---------------------------------- Summary: JBDS headless install no longer works in Jenkins / versionwatch unable to diff 9.0.0.Alpha2 w/ previous Key: JBIDE-19509 URL: https://issues.jboss.org/browse/JBIDE-19509 Project: Tools (JBoss Tools) Issue Type: Bug Components: qa Reporter: Nick Boldt JBDS headless install no longer works in Jenkins, so versionwatch is unable to diff 9.0.0.Alpha2 master builds w/ previous Alpha1 and 8.1.x builds. I've repeated exactly what the versionwatch script does locally and it's fine w/ JDK 7 and 8, so it's not a config problem. But in Jenkins, with VNC enabled (and when not) the headless install process repeatedly stalls out at step 2: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_Master/job/devstudio.versionwatch_master/1892/console} [ Starting automated installation ] [ Starting to unpack ] [ Processing package: P2 Director Application (1/3) ] [ Processing package: Red Hat JBoss Developer Studio 9.0.0.Alpha2 (2/3) ] [ Unpacking finished ] ... {code} But in the 8.1.luna branch, the job is fine: {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/devstudio.versionwatch_8.0.luna/363/console} +++ /qa/tools/opt/jdk1.6.0_last/bin/java -jar /qa/services/http/binaries/RHDS/builds/staging/devstudio.product_8.0.luna/installer/jboss-devstudio-8.1.0.GA-v20150324-2058-B454-installer-standalone.jar /home/hudson/static_build_env/jbds/versionwatch/installations/jbds-8.1.0.GA.install.xml [ Starting automated installation ] [ Starting to unpack ] [ Processing package: P2 Director Application (1/3) ] [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA (2/3) ] [ Processing package: Red Hat JBoss Developer Studio 8.1.0.GA Metadata Generation (3/3) ] [ Unpacking finished ] [ Creating shortcuts done. ] [ Add shortcuts to uninstaller done. ] [ Writing the uninstaller data ... ] [ Automated installation done ]{code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3387: ------------------------------------- this should not affect the master branch if https://github.com/jbdevstudio/jbdevstudio-product/pull/284 applied. > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Denis Golovin edited comment on JBDS-3387 at 3/24/15 6:47 PM: -------------------------------------------------------------- installer/pom.xml line 156 is the reason. was (Author: dgolovin): installer/pom.xml line156 is the reason. > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19480) For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19480?page=com.atlassian.jira.plugi... ] Alexey Kazakov closed JBIDE-19480. ---------------------------------- Assignee: Nick Boldt Resolution: Done All subtasks have been closed. Resolving. > For JBIDE 4.2.3.Final: Prepare for JBT 4.2.3.Final / JBDS 8.1.0.GA > ------------------------------------------------------------------ > > Key: JBIDE-19480 > URL: https://issues.jboss.org/browse/JBIDE-19480 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Labels: task > Fix For: 4.2.3.Final > > > For JBIDE 4.2.3.Final: Please perform the following tasks: > *If you contributed anything to the 4.2.3.Beta1 or 4.2.3.CR1 builds, you will need to perform the following task.* > 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.3.Final-SNAPSHOT{color}* > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.2.3.Final-SNAPSHOT</version> > </parent> > {code} > 3. Ensure you've built & run your plugin tests using the latest target platform version: > {code} > mvn clean verify -Dtpc.version=4.42.0.Final-SNAPSHOT # or, once released > mvn clean verify -Dtpc.version=4.42.0.Final > {code} > 2. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] > See also: JBDS-3385 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3387: ------------------------------------- installer/pom.xml line156 is the reason. > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3387: -------------------------------------- At least jgit depends on com.jcraft.jsch_0.1.51.v201410302000.jar. I don't know what plugin depends on com.jcraft.jsch_0.1.50.v201403120620.jar. But they are both in the TP. Let's do *NOT* remove any of them for JBDS 8.1.0 to not break anything in the last minute. Let's update versionwatch instead. We can investigate if we really need com.jcraft.jsch_0.1.50.v201403120620.jar in master/JBDS 9. > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3374) Remove org.eclipse.cvs feature from JBDS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3374?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3374. ---------------------------- Assignee: Nick Boldt Fix Version/s: 9.0.0.Alpha2 Resolution: Rejected Closing rejected based on Max's stats & the fact that other than "this is old" there's no reason to remove it. cc: [~burrsutter] [~ldimaggio] > Remove org.eclipse.cvs feature from JBDS > ---------------------------------------- > > Key: JBDS-3374 > URL: https://issues.jboss.org/browse/JBDS-3374 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha2 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import feature="org.eclipse.cvs"/> > {quote} > I can't see any reason why we'd do that in 2015. > Burr Sutter, Len DiMaggio, Max Rydahl Andersen : is there any client requirement about CVS support? -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3387 at 3/24/15 6:20 PM: ----------------------------------------------------------- Latest vwatch reports: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... (shows in red the dupes) https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... (shows known cases of IUs w/ multiple versions) was (Author: nickboldt): Latest vwatch report: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3387) JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3387?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3387: ---------------------------------- Latest vwatch report: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > JBDS installer includes two versions of com.jcraft.jsch - 0.1.50 and 0.1.51 > --------------------------------------------------------------------------- > > Key: JBDS-3387 > URL: https://issues.jboss.org/browse/JBDS-3387 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: 3rd-party-dependencies, installer, updatesite > Affects Versions: 8.1.0.CR1 > Reporter: Nick Boldt > Fix For: 8.1.0.GA, 9.0.0.Alpha2 > > > This has been a feature of our JBDS builds since 8.1.0.Beta1; is it a problem? > If so, we should remove one or the other; if not, we should update versionwatch to exclude this non-problem from the list of known cases where there are multiple versions. > cc: [~jpeterka] [~akazakov] > Who depends on these? > {code}com.jcraft.jsch_0.1.51.v201410302000.jar > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > Note that the update site only contains ONE of these IUs: > {code} > com.jcraft.jsch_0.1.50.v201403120620.jar{code} > But when you install from the installer, you get both on disk: > {code} > find . -name com.jcraft.jsch\* > ./studio/plugins/com.jcraft.jsch_0.1.51.v201410302000.jar > ./studio/plugins/com.jcraft.jsch_0.1.50.v201403120620.jar > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 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 March 2015