June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24581) suppress old pre-Final/pre-GA milestones from the downloads overview page

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24581?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24581: ------------------------------- Fix Version/s: 4.5.0.AM1 > suppress old pre-Final/pre-GA milestones from the downloads overview page > ------------------------------------------------------------------------- > > Key: JBIDE-24581 > URL: https://issues.jboss.org/browse/JBIDE-24581 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, website > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > > Recently I commented out a lot of old releases because they're old. > But as a result the what's new page [1] now shows a ton of old milestones as coming soon. > So we either need to hide old milestones from the what's new page, or find a way to suppress builds from appearing on the downloads page [2]. > [1] http://tools.jboss.org/documentation/whatsnew/ > [2] http://tools.jboss.org/downloads/overview.html -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-24540: ------------------------------------ Integration tests have no code dependency to any *.express.* plugin, thus I think removing integration tests can be done in separate jira: JBIDE-24580 > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Aurélien Pupier commented on JBDS-4105: --------------------------------------- what might be nice to have for m2e integration (after minimal hot deploy is working) is to have m2e being able to detect which changes requires a full redeploy and what can be done by just a normal hot deploy. > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24580) Remove integration tests of OpenShift 2 tooling

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-24580: ---------------------------------- Summary: Remove integration tests of OpenShift 2 tooling Key: JBIDE-24580 URL: https://issues.jboss.org/browse/JBIDE-24580 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, openshift Affects Versions: 4.5.0.AM1 Reporter: Radim Hopp Assignee: Radim Hopp Fix For: 4.5.x Once OpenShift 2 tooling is removed from Tools/Devstudio, integration tests should be removed too. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21727 at 6/26/17 10:57 AM: -------------------------------------------------------------- Too late to change in upstream as WTP 3.9.0 is done for Oxygen.0. Is we want to recategorize something we can suggest it for Oxygen.x or Photon.0.MX Note that this JIRA has sat for more than a year so I don't know if it's really a problem. :) Can you open a new JIRA to explain what's wrong, and to suggest what you'd like changed? was (Author: nickboldt): Too late to change in upstream as WTP 3.9.0 is done for Oxygen.0. Is we want to recategorize something we can suggest it for Oxygen.x or Photon.0.MX Note that this JIRA has sat for more than a year so I don't know if it's really a problem. :) > add OpenShift server adapter to downloadable WTP server adapters > ---------------------------------------------------------------- > > Key: JBIDE-21727 > URL: https://issues.jboss.org/browse/JBIDE-21727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png, screenshot-1.png > > > We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too. > Anything preventing us from doing so ? > Is there a workflow from New server that helps users to create openshift connection etc. ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21727) add OpenShift server adapter to downloadable WTP server adapters

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21727?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-21727 at 6/26/17 10:57 AM: -------------------------------------------------------------- Too late to change in upstream as WTP 3.9.0 is done for Oxygen.0. Is we want to recategorize something we can suggest it for Oxygen.x or Photon.0.MX Note that this JIRA has sat for more than a year so I don't know if it's really a problem. :) [~rhopp] Can you open a new JIRA to explain what's wrong, and to suggest what you'd like changed? cc: [~rob.stryker] was (Author: nickboldt): Too late to change in upstream as WTP 3.9.0 is done for Oxygen.0. Is we want to recategorize something we can suggest it for Oxygen.x or Photon.0.MX Note that this JIRA has sat for more than a year so I don't know if it's really a problem. :) Can you open a new JIRA to explain what's wrong, and to suggest what you'd like changed? > add OpenShift server adapter to downloadable WTP server adapters > ---------------------------------------------------------------- > > Key: JBIDE-21727 > URL: https://issues.jboss.org/browse/JBIDE-21727 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.5.0.AM1 > > Attachments: compositeArtifacts.xml, compositeContent.xml, mockup-change-1.png, mockup-change-2.png, openshiftv3-tools-server-adapter-manually-installed.png, openshiftv3-tools-server-adapter-no-license-found.png, openshiftv3-tools-server-adapter.png, screenshot-1.png > > > We have JBoss server adapters available in Eclise new Server wizard; would be great if we could put OpenShift in there too. > Anything preventing us from doing so ? > Is there a workflow from New server that helps users to create openshift connection etc. ? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-4105 at 6/26/17 10:56 AM: ------------------------------------------------------------------ in the Eclipse IDE we analyze the docker image metadata to discover the (deployment config) env variables keys and default values for * deployment dir (in the docker container): *com.redhat.deployments-dir* * debug mode enablement: *com.redhat.dev-mode* * debug port: *com.redhat.dev-mode.port* here's an expert showing what the nodejs image defines: {code} "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.access.redhat.com", "build-date": "2017-04-21T09:41:19.146364", "com.redhat.build-host": "ip-10-29-120-133.ec2.internal", "com.redhat.component": "rh-nodejs4-docker", "com.redhat.deployments-dir": "/opt/app-root/src", "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} was (Author: adietish): in the Eclipse IDE we analyze the docker image metadata to discover the (deployment config) env variables keys and default values for * deployment dir (in the docker container) * debug mode enablement * debug port here's an expert showing what the nodejs image defines: {code} "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.access.redhat.com", "build-date": "2017-04-21T09:41:19.146364", "com.redhat.build-host": "ip-10-29-120-133.ec2.internal", "com.redhat.component": "rh-nodejs4-docker", "com.redhat.deployments-dir": "/opt/app-root/src", "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24540) Remove Openshift 2 tooling

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24540?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24540: ------------------------------------ Thanks for the confirmation of what to remove, Jeff. Could you provide a PR to remove the integration tests? Are they in the jbosstools-openshift or the jbosstools-integration-tests project? Can you also confirm the TIMELINE for the removal? Is it for 11.0? 11.1? or 11.2? Are we waiting on new GA traffic data, or just removing it ASAP? > Remove Openshift 2 tooling > -------------------------- > > Key: JBIDE-24540 > URL: https://issues.jboss.org/browse/JBIDE-24540 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.5.0.AM1 > Reporter: Radim Hopp > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > End of support of Openshift 2 was in December 2016 [1] > There was a mail thread back in November/December 2016, where Todd stated, that Devstudio 11 would be the right release for dropping Openshift 2 support from Tools/Devstudio [2][3]. > Should we get PM/PgM approval once again just to be sure we are OK with removing Openshift 2 tooling from Tools/Devstudio? > [1] https://access.redhat.com/support/policy/updates/openshift/ > [2] http://post-office.corp.redhat.com/archives/devtools-program/2016-Novembe... > [3] http://post-office.corp.redhat.com/archives/devtools-program/2016-Decembe... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim commented on JBDS-4105: ---------------------------------------- in the Eclipse IDE we analyze the docker image metadata to discover the (deployment config) env variables keys and default values for * deployment dir (in the docker container) * debug mode enablement * debug port here's an expert showing what the nodejs image defines: {code} { "Id": "sha256:d40694a897c97e85df63aa8b7a84024dc1be4f8b15ed37b1740fa554150ae0dd", "RepoTags": [ "172.30.1.1:5000/node/nodejs:latest" ], "RepoDigests": [ "172.30.1.1:5000/node/nodejs@sha256:b6524cdc346b3601d8ba650ef77a6bf4c2d02b9a1be5d1af249af17cdbb056a2" ], ... "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.access.redhat.com", "build-date": "2017-04-21T09:41:19.146364", "com.redhat.build-host": "ip-10-29-120-133.ec2.internal", "com.redhat.component": "rh-nodejs4-docker", "com.redhat.deployments-dir": "/opt/app-root/src", "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4105) Provide m2e connector for io.fabric8:fabric8-maven-plugin

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-4105?page=com.atlassian.jira.plugin.... ] Andre Dietisheim edited comment on JBDS-4105 at 6/26/17 10:54 AM: ------------------------------------------------------------------ in the Eclipse IDE we analyze the docker image metadata to discover the (deployment config) env variables keys and default values for * deployment dir (in the docker container) * debug mode enablement * debug port here's an expert showing what the nodejs image defines: {code} "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.access.redhat.com", "build-date": "2017-04-21T09:41:19.146364", "com.redhat.build-host": "ip-10-29-120-133.ec2.internal", "com.redhat.component": "rh-nodejs4-docker", "com.redhat.deployments-dir": "/opt/app-root/src", "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} was (Author: adietish): in the Eclipse IDE we analyze the docker image metadata to discover the (deployment config) env variables keys and default values for * deployment dir (in the docker container) * debug mode enablement * debug port here's an expert showing what the nodejs image defines: {code} { "Id": "sha256:d40694a897c97e85df63aa8b7a84024dc1be4f8b15ed37b1740fa554150ae0dd", "RepoTags": [ "172.30.1.1:5000/node/nodejs:latest" ], "RepoDigests": [ "172.30.1.1:5000/node/nodejs@sha256:b6524cdc346b3601d8ba650ef77a6bf4c2d02b9a1be5d1af249af17cdbb056a2" ], ... "Labels": { "architecture": "x86_64", "authoritative-source-url": "registry.access.redhat.com", "build-date": "2017-04-21T09:41:19.146364", "com.redhat.build-host": "ip-10-29-120-133.ec2.internal", "com.redhat.component": "rh-nodejs4-docker", "com.redhat.deployments-dir": "/opt/app-root/src", "com.redhat.dev-mode": "DEV_MODE:false", "com.redhat.dev-mode.port": "DEBUG_PORT:5858", {code} > Provide m2e connector for io.fabric8:fabric8-maven-plugin > --------------------------------------------------------- > > Key: JBDS-4105 > URL: https://issues.jboss.org/browse/JBDS-4105 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: maven > Reporter: Aurélien Pupier > Fix For: 11.0.0.AM1 > > > iPaas Fuse is heavily using fabric8-maven-plugin. it will be nice to provide a m2e connector to have a better integration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 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 June 2017