January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-21301: --------------------------------------- Yeah, I got it on path {code} [mlabuda@dhcp-10-40-5-177 ~]$ echo $PATH /etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/mlabuda/.local/bin:/home/mlabuda/bin {code} and on OpenShift 3 preference page it is blank. > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-21301 at 1/25/16 3:54 AM: ---------------------------------------------------------------- Yeah, I got it on path {code} [mlabuda@dhcp-10-40-5-177 ~]$ echo $PATH /etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/mlabuda/.local/bin:/home/mlabuda/bin {code} and on OpenShift 3 preference page it is blank. Now tested on Beta2 build. was (Author: mlabuda): Yeah, I got it on path {code} [mlabuda@dhcp-10-40-5-177 ~]$ echo $PATH /etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/etc/alternatives/java_sdk_1.8.0/bin:/usr/share/maven/bin:/home/mlabuda/openshift/bin/oc:/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/mlabuda/.local/bin:/home/mlabuda/bin {code} and on OpenShift 3 preference page it is blank. > Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH > ------------------------------------------------------------------------------------- > > Key: JBIDE-21301 > URL: https://issues.jboss.org/browse/JBIDE-21301 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Priority: Minor > Labels: openshift_v3, preferences > Fix For: 4.3.1.Beta2 > > > In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3586) Cannot install Integration Stack from central

by Jan Richter (JIRA)

Jan Richter created JBDS-3586: --------------------------------- Summary: Cannot install Integration Stack from central Key: JBDS-3586 URL: https://issues.jboss.org/browse/JBDS-3586 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: central, updatesite Affects Versions: 9.1.0.Beta2 Reporter: Jan Richter Trying to install IS from central early access, I'm getting the following error: {noformat} An error occurred while collecting items to be installed session context was:(profile=jbds, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=). Problems downloading artifact: osgi.bundle,org.eclipse.graphiti.ui,0.13.0.v20150818-1354. Unpacking fails because intermediate file is empty: /tmp/work8606338891825741513/p2.optimizers.incoming8698731202719996837.jar {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-708) JBDS 9.1 Beta2: Update support page with fedora versions

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-708?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-708: ---------------------------------------- [~mhusnain], thanks. I took a look. The info on Fedora is ok. But I noticed you also modified OS X. Could you check that again? What you put in there clearly is not right: {quote} OS X Mavericks (10.10), OS X Yosemite (10.10), and OS X El Capitan (10.11) {quote} Should be: {quote} OS X Yosemite (10.10), and OS X El Capitan (10.11) {quote} > JBDS 9.1 Beta2: Update support page with fedora versions > -------------------------------------------------------- > > Key: TOOLSDOC-708 > URL: https://issues.jboss.org/browse/TOOLSDOC-708 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Components: General documentation issues > Affects Versions: 9.1 Beta2 > Reporter: Misha Ali > Assignee: Misha Ali > Labels: Support > Attachments: screenshot_support.png > > > We should update the support matrix of JBDS to include the latest Fedora releases: 22 and 23. At the same time, 21 can be dropped. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3560 at 1/25/16 1:25 AM: ----------------------------------------------------------- Upstream dali & wtp issues are resolved now. http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (and 3.2.0, too) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (but no 3.2.0) So... since the fixed version is in both TPs used for JBT 4.3.1.Beta2 / JBDS 9.1.0 Beta2, I would think we can resolve this for fixversion 9.1.0.Beta2. Any reason this is set to fixversion 9.1.0.CR1, and unresolved? Are we waiting for a new m2e release? JBIDE-21119 ? was (Author: nickboldt): http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (and 3.2.0, too) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (but no 3.2.0) So... since the fixed version is in both TPs used for JBT 4.3.1.Beta2 / JBDS 9.1.0 Beta2, I would think we can resolve this for fixversion 9.1.0.Beta2. Any reason this is set to fixversion 9.1.0.CR1, and unresolved? > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-21119: ------------------------------------ What version of m2e will include this fix? http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core_1.6.1.20150625-2338.jar http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core.ui_1.6.2.20150902-0002.jar > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21119) Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21119?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21119 at 1/25/16 1:24 AM: ------------------------------------------------------------- What version of m2e will include this fix? http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core_1.6.1.20150625-2338.jar http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core_1.6.2.20150902-0002.jar was (Author: nickboldt): What version of m2e will include this fix? http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core_1.6.1.20150625-2338.jar http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.eclipse.m2e.core.ui_1.6.2.20150902-0002.jar > Update 4.5y.x TP to m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21119 > URL: https://issues.jboss.org/browse/JBIDE-21119 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, target-platform, upstream > Affects Versions: 4.3.0.Final > Reporter: Nick Boldt > Assignee: Fred Bricon > Fix For: 4.3.1.CR1 > > > Fred said: {quote}So the m2e archetype feature also embeds a version of vulnerable commons-collections, that we need to fix upstream (even though it's not really vulnerable, just makes people cringy) -- JBDS-3560 > {quote} > So, we need a new version of m2e 1.6.x (with fix for apache commons collections 3.2.2 / COLLECTIONS-580 / JBDS-3560) and we can then mirror it and update the 4.50.x and 4.51.x TPs (for JBDS 9.1, not 9.0.1). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3560) Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3560?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3560: ---------------------------------- http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (and 3.2.0, too) http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.5... contains org.apache.commons.collections_3.2.2.v201511171945.jar (but no 3.2.0) So... since the fixed version is in both TPs used for JBT 4.3.1.Beta2 / JBDS 9.1.0 Beta2, I would think we can resolve this for fixversion 9.1.0.Beta2. Any reason this is set to fixversion 9.1.0.CR1, and unresolved? > Arbitrary remote code execution with InvokerTransformer (COLLECTIONS-580) > ------------------------------------------------------------------------- > > Key: JBDS-3560 > URL: https://issues.jboss.org/browse/JBDS-3560 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 8.1.0.GA, 9.0.0.GA, 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > Attachments: apache-commons-collections-in-JBDS7,8,9,10.png, apache-commons-collections-in-JBDS7,8,9,10_refs1.png, apache-commons-collections-in-JBDS7,8,9,10_refs10.png, apache-commons-collections-in-JBDS7,8,9,10_refs7.png, apache-commons-collections-in-JBDS7,8,9,10_refs8-IS-fuse.png, apache-commons-collections-in-JBDS7,8,9,10_refs8.png, apache-commons-collections-in-JBDS7,8,9,10_refs9.png, orbit.R20150519210750_vs_I20151117200049.log.txt, orbit.R20150519210750_vs_I20151117200049.log_onlyLatest.txt > > > This is a container issue to wrap & track https://issues.apache.org/jira/browse/COLLECTIONS-580 > Problem is that JBDS 9 (and probably 8 and 10 too) include org.apache.commons.collections 3.2.0.v2013030210310, which is affected by COLLECTIONS-580 - Arbitrary remote code execution with InvokerTransformer -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21559) Should can select a container to show logs when the pod contains more than 1 containers

by Chunyun Chen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21559?page=com.atlassian.jira.plugi... ] Chunyun Chen commented on JBIDE-21559: -------------------------------------- [~fbricon] There is a kibana pod which contains two containers, you can deploy the pod by following [1]. [1] https://github.com/openshift/origin-aggregated-logging/tree/master/deploy... > Should can select a container to show logs when the pod contains more than 1 containers > --------------------------------------------------------------------------------------- > > Key: JBIDE-21559 > URL: https://issues.jboss.org/browse/JBIDE-21559 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBoss OpenShift 3 Tools: 3.1.0.Beta2-v20160122-0251-B156 > Reporter: Chunyun Chen > Labels: openshift_v3 > > The existing issue: > 1.EXEC: Deploy a pod which contains more than 1 containers > 2.EXEC: Expand the related service tree view in "OpenShift Explorer" > 3.EXEC: Right click above pod -> click "Pod Log..." > 4.ASSERT: Will meet some errors in "Console" window like "Error from server: a container name must be specified for pod logging-kibana-1-icxl2" > So, we need find a method for user to specify a container to show logs when the pod has more than 1 containers. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21407) staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21407?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-21407. ------------------------------ Resolution: Done Disable/re-enable steps worked fine for Beta2 staging so closing this. > staging/release guides should generate task jiras to remind releng to re-enable disabled jobs once staging or release is done > ----------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21407 > URL: https://issues.jboss.org/browse/JBIDE-21407 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.1.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.1.Beta2 > > > Amend both staging and release guides such that disabled jobs are appropriately re-enabled at the correct time: once staging/release announcement emails are sent *if there's a planned future milestone*. > * re-enable job > * set correct github branch > * upversion dependencies (eg., releng scripts) > * upversion target platforms / Central version > * ...? > Verify this is correctly done for 4.3.1.Beta2, as that will also require the same on/off/on steps as were done for 4.3.1.Beta1 (JBIDE-21392). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 4 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