July 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3893) Refactor target platforms from jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3893?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-3893. ---------------------------- Fix Version/s: 11.0.0.GA (was: 11.x) Resolution: Duplicate Issue Dupe of JBDS-3894 > Refactor target platforms from jbdevstudio to devstudio > ------------------------------------------------------- > > Key: JBDS-3893 > URL: https://issues.jboss.org/browse/JBDS-3893 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.0.0.GA > > > In https://github.com/jbosstools/jbosstools-target-platforms/commits/4.60.x we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio. > Affected: publishing/staging/release scripts, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Description: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one * refactoring as per JBDS-3894 was: Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one > eliminate devstudio target platform; reuse jbosstools target platform > --------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * jbosstools-discovery repo - remove unneeded configuration / folders > * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts > * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one > * refactoring as per JBDS-3894 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3894) Refactor discovery plugins/TPs from jbds/jbdevstudio to devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3894?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3894: ----------------------------- Fix Version/s: 11.1.0.AM1 (was: 11.x) > Refactor discovery plugins/TPs from jbds/jbdevstudio to devstudio > ----------------------------------------------------------------- > > Key: JBDS-3894 > URL: https://issues.jboss.org/browse/JBDS-3894 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: central-update, target-platform, updatesite > Affects Versions: 10.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.1.0.AM1 > > > In https://github.com/jbosstools/jbosstools-discovery/ we should finally adopt consistent naming/branding for the devstudio target platforms, using devstudio instead of jbdevstudio and jbds. > Affected: publishing/staging/release scripts, discovery sites, jenkins jobs, etc. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20046) find lost patches and check that SHAs have been built before publishing to staging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20046?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-20046. ------------------------------ Resolution: Done Last part of this proposal isn't going to get done. But the first 2 of 3 are, so closing. > find lost patches and check that SHAs have been built before publishing to staging > ---------------------------------------------------------------------------------- > > Key: JBIDE-20046 > URL: https://issues.jboss.org/browse/JBIDE-20046 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Suggested by [~rob.stryker] to avoid having situations where jobs are disabled because no one is maintaining the code & we end up with something like JBIDE-20041, where last year's Freemarker is included in JBT 4.3.0.Beta1 instead of the latest stuff. > {quote} > [10:36:50 AM] Rob Stryker: would it be possible to make a script that runs once a week checking for commits and firing emails indicating the jobs should be re-enabled? > [10:37:50 AM] Rob Stryker: if job is enabled, dont even bother to check/notify > [10:37:57 AM] Rob Stryker: if job is disabled, then check for new commits > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20046) create jiralint-like notifier that can alert if changes in a branch have not been built after X days

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20046?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20046: ------------------------------- Fix Version/s: 4.5.0.Final (was: 4.4.x) > create jiralint-like notifier that can alert if changes in a branch have not been built after X days > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20046 > URL: https://issues.jboss.org/browse/JBIDE-20046 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Suggested by [~rob.stryker] to avoid having situations where jobs are disabled because no one is maintaining the code & we end up with something like JBIDE-20041, where last year's Freemarker is included in JBT 4.3.0.Beta1 instead of the latest stuff. > {quote} > [10:36:50 AM] Rob Stryker: would it be possible to make a script that runs once a week checking for commits and firing emails indicating the jobs should be re-enabled? > [10:37:50 AM] Rob Stryker: if job is enabled, dont even bother to check/notify > [10:37:57 AM] Rob Stryker: if job is disabled, then check for new commits > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20046) find lost patches and check that SHAs have been built before publishing to staging

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20046?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20046: ------------------------------- Summary: find lost patches and check that SHAs have been built before publishing to staging (was: create jiralint-like notifier that can alert if changes in a branch have not been built after X days) > find lost patches and check that SHAs have been built before publishing to staging > ---------------------------------------------------------------------------------- > > Key: JBIDE-20046 > URL: https://issues.jboss.org/browse/JBIDE-20046 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Suggested by [~rob.stryker] to avoid having situations where jobs are disabled because no one is maintaining the code & we end up with something like JBIDE-20041, where last year's Freemarker is included in JBT 4.3.0.Beta1 instead of the latest stuff. > {quote} > [10:36:50 AM] Rob Stryker: would it be possible to make a script that runs once a week checking for commits and firing emails indicating the jobs should be re-enabled? > [10:37:50 AM] Rob Stryker: if job is enabled, dont even bother to check/notify > [10:37:57 AM] Rob Stryker: if job is disabled, then check for new commits > {quote} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24772: ------------------------------- Fix Version/s: 4.5.1.AM1 > eliminate devstudio target platform; reuse jbosstools target platform > --------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Fix For: 4.5.1.AM1 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * jbosstools-discovery repo - remove unneeded configuration / folders > * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts > * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24772?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24772: ---------------------------------- Assignee: Nick Boldt > eliminate devstudio target platform; reuse jbosstools target platform > --------------------------------------------------------------------- > > Key: JBIDE-24772 > URL: https://issues.jboss.org/browse/JBIDE-24772 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 4.5.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. > Changes: > * jbosstools-discovery repo - remove unneeded configuration / folders > * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that > * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts > * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24772) eliminate devstudio target platform; reuse jbosstools target platform

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-24772: ---------------------------------- Summary: eliminate devstudio target platform; reuse jbosstools target platform Key: JBIDE-24772 URL: https://issues.jboss.org/browse/JBIDE-24772 Project: Tools (JBoss Tools) Issue Type: Bug Components: build, target-platform Affects Versions: 4.5.0.Final Reporter: Nick Boldt Now that jbosstoolstarget and jbdevstudiotarget are the same - JBDS-444- - we can eliminate one of them and simply reuse the same artifact in two places. Changes: * jbosstools-discovery repo - remove unneeded configuration / folders * job(s) that publish target platforms to dl.jb.o and ds.rh.com - copy the jbosstools TP to ds.rh.com instead of building a different one & publishing that * job(s) / release guide steps that rename/copy target platforms to staging / development / stable / static - change source of TPs to copy/rename to reuse the jbosstools artifacts * jbdevstudio-product/pom.xml - point at jbosstoolstarget instead of jbdevstudio one -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23350?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23350. --------------------------------- It seems this is really out of date (Marian confirms). > Deploy Docker Wizard: Prompt to enter credentials contains Finish button > ------------------------------------------------------------------------ > > Key: JBIDE-23350 > URL: https://issues.jboss.org/browse/JBIDE-23350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.5.0.AM1 > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 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