May 2017 - jbosstools-issues - Jboss List Archives

[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 commented on JBIDE-24382: ------------------------------------ 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

1
0
0 / 0

[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: ------------------------------- Description: 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 was: 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. > 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

1
0
0 / 0

[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: ------------------------------- Description: 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. was: 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] > 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. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24383: ------------------------------------- Description: now that https://openshift.com is launched we should provide it as default server in the connection wizard. (was: now that https://openshift.io is launched we should provide it as default server in the connection wizard.) > Connection wizard: offer openshift.com as default server > -------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > now that https://openshift.com is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24383: ------------------------------------- Summary: Connection wizard: offer openshift.com as default server (was: Connection wizard: offer openshift.io as default server) > Connection wizard: offer openshift.com as default server > -------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > now that https://openshift.io is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24383) Connection wizard: offer openshift.com as default server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24383?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24383: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Connection wizard: offer openshift.com as default server > -------------------------------------------------------- > > Key: JBIDE-24383 > URL: https://issues.jboss.org/browse/JBIDE-24383 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > now that https://openshift.com is launched we should provide it as default server in the connection wizard. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24373?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24373: ------------------------------------------ merged into jbosstools-4.4.x and cherry-picked into master > Can't push an image to the CDK3 Docker registry > ----------------------------------------------- > > Key: JBIDE-24373 > URL: https://issues.jboss.org/browse/JBIDE-24373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. > Steps to reproduce: > # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) > # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address ("minishift docker-env" should tell you about this url) > # Build your own Docker image on the CDK3 Docker connection > # Deploy that image and select Push to registry: a timeout will occur after 30s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24373) Can't push an image to the CDK3 Docker registry

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24373?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24373: ------------------------------------- Fix Version/s: 4.5.0.AM1 > Can't push an image to the CDK3 Docker registry > ----------------------------------------------- > > Key: JBIDE-24373 > URL: https://issues.jboss.org/browse/JBIDE-24373 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.4.AM3 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: openshift, openshift_v3 > Fix For: 4.4.4.Final, 4.5.0.AM1 > > > Pushing an image to the CDK3 Docker registry is not possible. When the image is tagged, the registry port is not used thus Docker will try to contact the CDK Docker registry in port 80 causing a timeout to occur at the UI level. > Steps to reproduce: > # Create a Docker and OpenShift connection to CDK3 (using the server adapter or manually) > # Edit the OpenShift connection and add http://172.30.1.1:5000 as the registry address ("minishift docker-env" should tell you about this url) > # Build your own Docker image on the CDK3 Docker connection > # Deploy that image and select Push to registry: a timeout will occur after 30s -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24301) Error while building jbosstools-openshift-4.4.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24301?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24301: ------------------------------------ You might also enjoy this document on how to use our target platform: https://github.com/jbosstools/jbosstools-devdoc/blob/master/building/targ... Note too that next week the -SNAPSHOT will be removed and a 4.63.0.Final target platform will be released. Oh, and finally, make sure you use the correct target platform for the version of jbosstools / devstudio you're building. * 4.63.x is based on Eclipse 4.6.3 (Neon.3). * 4.70.x is based on Eclipse 4.7 (Oxygen) - currently contains Oxygen.0.M5 > 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

1
0
0 / 0

[JBoss JIRA] (JBTIS-1100) Teiid Designer - remove unnecessary feature pull of org.jboss.tools.foundation.security.linux.feature

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1100?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1100: ----------------------------------- https://github.com/Teiid-Designer/teiid-designer/pull/571 > Teiid Designer - remove unnecessary feature pull of org.jboss.tools.foundation.security.linux.feature > ----------------------------------------------------------------------------------------------------- > > Key: JBTIS-1100 > URL: https://issues.jboss.org/browse/JBTIS-1100 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: teiid > Affects Versions: 10.3.0.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 10.4.0.CR1 > > > The teiid-designer feature is causing the wrong org.jboss.tools.foundation.security.linux.feature to be pulled into the Integration Stack. It's accessible via the IS target platform - just need to remove it from the TD feature.xml. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 May 2017