[JBoss JIRA] (JBTIS-1101) Cannot install reddeer feature
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1101:
----------------------------------------
Summary: Cannot install reddeer feature
Key: JBTIS-1101
URL: https://issues.jboss.org/browse/JBTIS-1101
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 10.3.0.CR1
Reporter: Andrej Podhradsky
Fix For: 10.3.0.GA
The following feature cannot be installed
- org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final
The error is
{code}
Your original request has been modified.
"JBoss Tools Foundation Security for Linux" will be ignored because a newer version is already installed.
Cannot complete the install because one or more required items could not be found.
Software being installed: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
Missing requirement: RedDeer GEF Component 1.2.1.Final (org.jboss.reddeer.gef 1.2.1.Final) requires 'bundle org.jboss.reddeer.workbench [1.2.0,1.3.0)' but it could not be found
Cannot satisfy dependency:
From: RedDeer GEF/Graphiti Feature 1.2.1.Final (org.jboss.reddeer.graphiti.feature.feature.group 1.2.1.Final)
To: org.jboss.reddeer.gef [1.2.1.Final]
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a project without route specified
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Aurélien Pupier edited comment on JBIDE-24306 at 5/4/17 4:44 AM:
-----------------------------------------------------------------
in my steps to reproduce, I mentioned creating a "Fuse integration project" not an OpenShift project.
you can see it how here: https://www.youtube.com/watch?v=Ko4mNaQsCvI
You will need to activate staging repositories before as FIS 2.0 patch is not released yet (Window->Preferences -> Fuse Tooling -> Staging repositories, check the box)
or to choose the 2.18.1.redhat-000012 version (which is no more the default one)
was (Author: aurelien.pupier):
in my steps to reproduce, I mentioned creating a "Fuse integration project" not an OpenShift project.
you can see it how here: https://www.youtube.com/watch?v=Ko4mNaQsCvI
You will need to activate staging repositories before as FIS 2.0 patch is nto released yet (Window->Preferences -> Fuse Tooling -> Staging repositories, check the box)
> Cannot connect to JMX through OpenShift Server adapter to a project without route specified
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3
by jyoti tumsare (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ]
jyoti tumsare commented on JBIDE-24301:
---------------------------------------
yes sir, you noticed correctly.
I am adding below link in install new software
http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.6...
> Error while building jbosstools-openshift-4.4.3
> -----------------------------------------------
>
> Key: JBIDE-24301
> URL: https://issues.jboss.org/browse/JBIDE-24301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift
> Affects Versions: 4.4.3.Final
> Reporter: jyoti tumsare
> Assignee: Dmitrii Bocharov
> Fix For: 4.5.0.AM1
>
> Attachments: issues.PNG, issues.txt, target-platform.png
>
>
> To build jbosstools-openshift-4.4.3 I followed following steps
> 1. I clone jbosstools-base and jbosstools-server which are required for the building jbosstools-openshift-4.4.3.
> 2. while executing the jbosstools-base I got error "Missing requirement: org.jboss.tools.common.core 3.8.3.qualifier requires 'bundle org.jboss.tools.foundation.core 1.3.3' but it could not be found".
> 3. I build the org.jboss.tools.foundation.core 1.3.3 plugin and add into eclipse plugin folder and restart the eclipse IDE still facing the isuue.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by jyoti tumsare (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
jyoti tumsare commented on JBIDE-24382:
---------------------------------------
sir, can you please tell me the steps to build jbosstools-openshift-4.4.3 in eclipse Neon.2 Release (4.6.2).
I mean what is prerequisite and what are the other repository need to run.
What are the exact stpes need to follow, because I am facing lots of issues while buiding the jbosstools-openshift-4.4.3 source code.
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.Final
>
> Attachments: devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a project without route specified
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Aurélien Pupier commented on JBIDE-24306:
-----------------------------------------
in my steps to reproduce, I mentioned creating a "Fuse integration project" not an OpenShift project.
you can see it how here: https://www.youtube.com/watch?v=Ko4mNaQsCvI
You will need to activate staging repositories before as FIS 2.0 patch is nto released yet (Window->Preferences -> Fuse Tooling -> Staging repositories, check the box)
> Cannot connect to JMX through OpenShift Server adapter to a project without route specified
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a project without route specified
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24306:
-------------------------------------
[~aurelien.pupier] I'm having trouble replicating your specific steps to replicate, specifically:
> choose OpenShift template on last wizard page
My steps:
1) Start cdk
2) go to openshift explorer, right-click openshift connection, new -> project (name it test)
3) right-click on project "test", select new application
4) On the FIRST page, there's an option to choose templates. I choose `fis-java-openshift:2.0` and proceed to press next several times
5) The last page of the wizard asks me to create resource labels, not choose an openshift template?
Basically, I'm really baffled here. Think you can set up a screencast?
Thanks.
> Cannot connect to JMX through OpenShift Server adapter to a project without route specified
> -------------------------------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-24382:
-------------------------------
Attachment: p2diff.txt
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.Final
>
> Attachments: devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png, p2diff.txt
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24382) Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24382?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-24382 at 5/3/17 4:57 PM:
------------------------------------------------------------
PRs to make openshift and devstudio depend on latest m2e and docker tools:
https://github.com/jbdevstudio/jbdevstudio-product/pull/449
https://github.com/jbdevstudio/jbdevstudio-product/pull/448
https://github.com/jbosstools/jbosstools-openshift/pull/1492
https://github.com/jbosstools/jbosstools-openshift/pull/1493
Need to first get the newer Docker Tools into the JBT 4.60.x target platforms or builds will fail:
https://github.com/jbosstools/jbosstools-target-platforms/pull/257 (4.60.x)
was (Author: nickboldt):
PRs to make openshift and devstudio depend on latest m2e and docker tools:
https://github.com/jbdevstudio/jbdevstudio-product/pull/449
https://github.com/jbdevstudio/jbdevstudio-product/pull/448
https://github.com/jbosstools/jbosstools-openshift/pull/1492
https://github.com/jbosstools/jbosstools-openshift/pull/1493
Need to first get the newer Docker Tools into the JBT 4.60.x target platforms or builds will fail. Coming up next.
> Update Neon.3 target platform using Docker 2.3.0, not 2.3.1
> -----------------------------------------------------------
>
> Key: JBIDE-24382
> URL: https://issues.jboss.org/browse/JBIDE-24382
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, docker, target-platform
> Affects Versions: 4.4.4.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.4.Final
>
> Attachments: devstudio-1040GAvsAM3.png, install-devstudio1040ga-ci-snapshot-byoe-docker2.3.0.20170307.png, install-devstudio1040ga-ci-snapshot-byoe.png
>
>
> 1. Mirror http://download.eclipse.org/linuxtools/update-docker-neon3respinb to http://download.jboss.org/jbosstools/updates/requirements/docker/2.3.0.20... (Done today.)
> 2. Update jbt/ds 4.63.x TPs to use this Neon.3-respin-b version of Docker Tools (PR forthcoming.)
> cc: [~jjohnstn] [~lvalach] [~odockal]
> Why, you ask?
> Well, the 2.3.0.20170425 rebuild of Docker Tools fixes wiring issues w.r.t. docker by depending on OLDER dependencies like spotify.docker 3.4, httpcomponents.httpcore (and httpclient), plus backlevels jnr.* plugins too.
> Without this fix [1], installation may pull in an older version of Docker Tools, which depends on newer dependencies. This forces the old deps and the newer feature to be installed and used.
> [1] https://github.com/jbosstools/jbosstools-openshift/pull/1492 & https://github.com/jbosstools/jbosstools-openshift/pull/1493
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months