February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23867) OCBinary: is mixing platform independent with dependent code

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23867?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23867. --------------------------------- Fix Version/s: 4.4.3.Final Resolution: Done > OCBinary: is mixing platform independent with dependent code > ------------------------------------------------------------ > > Key: JBIDE-23867 > URL: https://issues.jboss.org/browse/JBIDE-23867 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.3.Final > > > OCBinary is suing enums for the different platform. The platform instance is chosen right when you get the instance that you want to work with: > {code} > OCBinary#getInstance > {code} > {code} > public static OCBinary getInstance() { > if (SystemUtils.IS_OS_WINDOWS) { > return WINDOWS; > } else { > return OTHER; > } > } > {code} > But then, latter code (that was introduced later in #getSystemPathLocation ignoring it and start being platform independent again, even setting the default to be linux: > {code} > public String getSystemPathLocation() { > if (locationBinary == null) { > this.locationBinary = new CommandLocationBinary("oc"); > locationBinary.addPlatformLocation(Platform.OS_LINUX, OC_DEFAULTLOCATION_LINUX); > locationBinary.setDefaultPlatform(Platform.OS_LINUX); > } > return locationBinary.findLocation(); > } > {code} > Even worse is that the above code hard-codes the oc binary to be "oc" while the enum for windows is defining it as "oc.exe" -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23862: ------------------------------------------ added a fix to osjc in https://github.com/openshift/openshift-restclient-java/pull/255 deployed openshift-restclient-java 5.5.0-SNAPSHOT to repository.jboss.org > Server adapter: if "oc" in preferences is set to path with a " " syncing fails > ------------------------------------------------------------------------------ > > Key: JBIDE-23862 > URL: https://issues.jboss.org/browse/JBIDE-23862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23862?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23862: ------------------------------------------ fixing in JBT isnt a great option because once we add the quotes we have to remove them when ex. validator are applied. > Server adapter: if "oc" in preferences is set to path with a " " syncing fails > ------------------------------------------------------------------------------ > > Key: JBIDE-23862 > URL: https://issues.jboss.org/browse/JBIDE-23862 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.4.3.Final > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23860) Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23860?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23860: ------------------------------------------ https://github.com/jbosstools/jbosstools-openshift/commit/c9a1df6409d3852... committed a fix for the unit test > Unit tests: CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials is failing > --------------------------------------------------------------------------------- > > Key: JBIDE-23860 > URL: https://issues.jboss.org/browse/JBIDE-23860 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.3.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.3.Final > > > starting with [#1815|https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBossTools_Master/job/jbosstools-openshift_master/1815/] the jenkins build for openshift started to fail with an error in the unit-tests: > {code} > Failed tests: > CDKOpenshiftUtilityTest.testOpenshiftConnectionCredentials:57 expected:<[openshift-dev]> but was:<[test]> > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-23536: ---------------------------------- Assignee: Nick Boldt (was: Jeff MAURY) > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23536) components.py should store the assigned user

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23536?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23536: ------------------------------------ This should protect creation of JIRAs and return the JIRA # even if the user can't assign the issues to the componentLead: https://github.com/jbosstools/jbosstools-build-ci/pull/159/files?w=1 > components.py should store the assigned user > -------------------------------------------- > > Key: JBIDE-23536 > URL: https://issues.jboss.org/browse/JBIDE-23536 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: build, release, release-eng > Fix For: 4.4.3.Final > > Attachments: run.log > > > The file components.py is used when created JIRAs during the release process. One JIRA is created per component. But those JIRAs are not initially assigned to a user, so the user of the scripts (createnewandnotworthy,....) must update all the created JIRAs. If the file stored as well the JIRA user id, then this could be done automatically -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23880) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23880: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build] Key: JBIDE-23880 URL: https://issues.jboss.org/browse/JBIDE-23880 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [build]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23879) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23879: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build] Key: JBIDE-23879 URL: https://issues.jboss.org/browse/JBIDE-23879 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [build]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23877) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23877: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build] Key: JBIDE-23877 URL: https://issues.jboss.org/browse/JBIDE-23877 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [build]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23878) For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created JBIDE-23878: ------------------------------------------- Summary: For JBIDE 4.4.3.Final: Prepare for 4.4.3.Final / 10.3.0.GA [build] Key: JBIDE-23878 URL: https://issues.jboss.org/browse/JBIDE-23878 Project: Tools (JBoss Tools) Issue Type: Task Components: build Reporter: Friendly Jira Robot Priority: Blocker Fix For: 4.4.3.Final For JBIDE 4.4.3.Final [build]: Please perform the following tasks: 1. Check out your existing *{color:orange}master{color}* branch: {code} git checkout master {code} 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.4.3.Final-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.4.3.Final-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:orange}4.4.3.Final-SNAPSHOT{color}* in your *{color:orange}master{color}* branch 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. {code} mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.60.2.Final {code} mvn clean verify -Dtpc.version=4.60.2.Final {code} 5. Close (do not resolve) this JIRA when done. 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for build task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 February 2017