July 2017 - jbosstools-issues - Jboss List Archives

[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 edited comment on JBIDE-24540 at 7/2/17 4:31 PM: ------------------------------------------------------------ I've removed the features from the OOTB installation of JBT and devstudio (CoreTools / Abridged categories, installer contents): * https://github.com/jbosstools/jbosstools-build-sites/commits/master * https://github.com/jbdevstudio/jbdevstudio-product/commit/a5385915ef320d0... And I've marked the Openshift v2 tooling connectors in Central as deprecated. * https://github.com/jbosstools/jbosstools-discovery/commit/6460ca486f94d1d... I've also marked the features themselves deprecated: * https://github.com/jbosstools/jbosstools-openshift/pull/1522 [~jeffmaury] [~rpdavis] anything else you'd like done here? was (Author: nickboldt): I've removed the features from the OOTB installation of JBT and devstudio (CoreTools / Abridged categories, installer contents): * https://github.com/jbosstools/jbosstools-build-sites/commits/master * https://github.com/jbdevstudio/jbdevstudio-product/commit/a5385915ef320d0... And I've marked the Openshift v2 tooling connectors in Central as deprecated. * https://github.com/jbosstools/jbosstools-discovery/commit/6460ca486f94d1d... I've also marked the features themselves deprecated: https://github.com/jbosstools/jbosstools-openshift/pull/1522 [~jeffmaury] [~rpdavis] anything else you'd like done here? > 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] (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: ------------------------------------ I've removed the features from the OOTB installation of JBT and devstudio (CoreTools / Abridged categories, installer contents): *https://github.com/jbosstools/jbosstools-build-sites/commits/master * https://github.com/jbdevstudio/jbdevstudio-product/commit/a5385915ef320d0... And I've marked the Openshift v2 tooling connectors in Central as deprecated. * https://github.com/jbosstools/jbosstools-discovery/commit/6460ca486f94d1d... I've also marked the features themselves deprecated: https://github.com/jbosstools/jbosstools-openshift/pull/1522 [~jeffmaury] [~rpdavis] anything else you'd like done here? > 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] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24640: ------------------------------- Attachment: good-dev-site-contents.png > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: bad-dev-site-contents.png, good-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24640: ------------------------------------ Fixed: https://github.com/jbdevstudio/jbdevstudio-ci/commit/08fb7e1613a016c2c43b... https://github.com/jbdevstudio/jbdevstudio-ci/commit/11b57c8c23613a73e3bb... !good-dev-site-contents.png|thumbnail! > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: bad-dev-site-contents.png, good-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-24640. ------------------------------ Resolution: Done > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: bad-dev-site-contents.png, good-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24640: ------------------------------- Fix Version/s: 4.5.0.AM1 > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: bad-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24640: ---------------------------------- Assignee: Nick Boldt > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM1 > > Attachments: bad-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24640: ------------------------------- Description: When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: !bad-dev-site-contents.png|thumbnail! was: When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Attachments: bad-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: > !bad-dev-site-contents.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24640: ---------------------------------- Summary: when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths Key: JBIDE-24640 URL: https://issues.jboss.org/browse/JBIDE-24640 Project: Tools (JBoss Tools) Issue Type: Bug Components: build Affects Versions: 4.5.0.AM1 Reporter: Nick Boldt Attachments: bad-dev-site-contents.png When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24640) when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24640?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24640: ------------------------------- Attachment: bad-dev-site-contents.png > when publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths > -------------------------------------------------------------------------------------------- > > Key: JBIDE-24640 > URL: https://issues.jboss.org/browse/JBIDE-24640 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Attachments: bad-dev-site-contents.png > > > When publishing from AM1d staging to AM1 development, URLs not updated to use /static/ paths. > Thus the staging site, when copied, was not correctly sed-replaced, and we end up with this in the dev site: -- 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 July 2017