January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21428: ------------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21428 > URL: https://issues.jboss.org/browse/JBIDE-21428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21428: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/888, https://github.com/jbosstools/jbosstools-openshift/pull/889 (was: https://github.com/jbosstools/jbosstools-openshift/pull/888) > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21428 > URL: https://issues.jboss.org/browse/JBIDE-21428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.Beta2 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21428: ----------------------------------------------- Sure, [~adietish], please make the best of it! > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21428 > URL: https://issues.jboss.org/browse/JBIDE-21428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta2 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21428: ------------------------------------------ [~scabanovich] your comments on #performDefault are insightful. On the other hand I dont think that we should change OpenShiftCorePreferences.getOCBinaryLocation() as you suggested since this changes the scope of this class, it wont only get preference values any longer. I have a change pending where I added a lookup to the preferences in OCBinaryName (which I renamed to OCBinary). OCBinary would then become able to get the location from preferences or look it up in $PATH which seems more convenient to me. I suggest that we mix your change in the preference page and my in OCBinary. > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21428 > URL: https://issues.jboss.org/browse/JBIDE-21428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta2 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21428) Server adapter: cannot publish, cannot find "oc" executable

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21428?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21428: ----------------------------------------------- [~adietish], [~fbricon], please take a look at the pull request. It turns out, that Eclipse preference input fields which we extend, always change instance value on performDefaults() and on any manual change, even if then it is returned manually to default! So, since it is important to have no instance value until it is changed from default, I changed performDefaults() and performOk() to clean it. I hope it may help. > Server adapter: cannot publish, cannot find "oc" executable > ----------------------------------------------------------- > > Key: JBIDE-21428 > URL: https://issues.jboss.org/browse/JBIDE-21428 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.Beta2 > > Attachments: could-not-sync-error.png, oc-binary-preferences.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-21290: -------------------------------- Component/s: upstream > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21290: ------------------------------------- I've made a commit changing the hard-coded version to 2.0 for now, until upstream provides some sort of API. > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, runtime-detection > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.3.1.Beta2, 4.4.0.Alpha1 > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20485) create python script to generate JIRA+email for release steps

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20485?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20485. ------------------------------ Fix Version/s: 4.3.0.Final (was: 4.3.x) Resolution: Won't Fix Closing / not required. > create python script to generate JIRA+email for release steps > ------------------------------------------------------------- > > Key: JBIDE-20485 > URL: https://issues.jboss.org/browse/JBIDE-20485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.0.Final > > > In https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/bin we have scripts that generate MULTIPLE JIRAs or generate COMPLICATED JIRAs, but Max and Alexey has requested that we have a script to generate SINGLE Task JIRAs, assigned to project lead so it can be triaged and tracked instead of being lost in mail to individuals / mailing lists. > Create task JIRA to track tagging operation as part of release of JBT; assign to project lead (Alexey) & add watchers (Nick, Mickael, Fred, Max, Denis); send FYI email to jbosstools-dev@ list -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20485) create python script to generate JIRA+email for release steps

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20485?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20485: ---------------------------------------- Agree. We don't need any new JIRAs or emails for component leads to tag the branch. The components leads do not tag anymore. Thanks to https://github.com/jbosstools/jbosstools-build-ci/blob/jbosstools-4.4.x/u... > create python script to generate JIRA+email for release steps > ------------------------------------------------------------- > > Key: JBIDE-20485 > URL: https://issues.jboss.org/browse/JBIDE-20485 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.3.x > > > In https://github.com/jbdevstudio/jbdevstudio-ci/tree/master/bin we have scripts that generate MULTIPLE JIRAs or generate COMPLICATED JIRAs, but Max and Alexey has requested that we have a script to generate SINGLE Task JIRAs, assigned to project lead so it can be triaged and tracked instead of being lost in mail to individuals / mailing lists. > Create task JIRA to track tagging operation as part of release of JBT; assign to project lead (Alexey) & add watchers (Nick, Mickael, Fred, Max, Denis); send FYI email to jbosstools-dev@ list -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (LOCUS-49) Add jaxb-xjc and jaxb-impl to locus

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/LOCUS-49?page=com.atlassian.jira.plugin.s... ] Nick Boldt updated LOCUS-49: ---------------------------- Fix Version/s: 1.5.0 > Add jaxb-xjc and jaxb-impl to locus > ----------------------------------- > > Key: LOCUS-49 > URL: https://issues.jboss.org/browse/LOCUS-49 > Project: JBoss Tools Locus > Issue Type: Feature Request > Affects Versions: 1.4.0 > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 1.5.0 > > > Request addition of jaxb-xjc and jaxb-impl into Mars/ locus. > This completes the initial request from Fuse Data Transformation and allows the removal of locally captured lib versions of jaxb-xjc and jaxb-impl in favor of JBTIS TP dependencies. > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-xjc/2.2.7/jaxb-xjc-2... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > https://repo1.maven.org/maven2/com/sun/xml/bind/jaxb-impl/2.2.7/jaxb-impl... > This is needed for Mars/ 9.0.x JBDSIS target platform inclusion. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 January 2016