June 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24570) Fix mylyn prcheck job

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24570?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24570: ---------------------------------- Fix Version/s: 4.5.0.AM1 > Fix mylyn prcheck job > --------------------- > > Key: JBIDE-24570 > URL: https://issues.jboss.org/browse/JBIDE-24570 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24576) Create label for releng slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24576?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-24576: --------------------------------------- Merge Request is merged: https://gitlab.mw.lab.eng.bos.redhat.com/dev-platform/mwqa-cloud-slaves/m... Closing > Create label for releng slaves > ------------------------------ > > Key: JBIDE-24576 > URL: https://issues.jboss.org/browse/JBIDE-24576 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.AM2 > > > Create new label for releng slaves to have one repo. Label should have ssh keys for releng slaves. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24576) Create label for releng slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24576?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-24576. --------------------------------- Resolution: Done > Create label for releng slaves > ------------------------------ > > Key: JBIDE-24576 > URL: https://issues.jboss.org/browse/JBIDE-24576 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.5.0.AM2 > > > Create new label for releng slaves to have one repo. Label should have ssh keys for releng slaves. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24575) Prepare missing Linux x86 images for slaves

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24575?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24575: ---------------------------------- Summary: Prepare missing Linux x86 images for slaves (was: Prepare missing x86 images for slaves) > Prepare missing Linux x86 images for slaves > ------------------------------------------- > > Key: JBIDE-24575 > URL: https://issues.jboss.org/browse/JBIDE-24575 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests > Affects Versions: 4.5.0.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24519 at 6/29/17 4:59 PM: ------------------------------------------------------------- See my comment above. Lots more to do: * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs: DONE was (Author: nickboldt): See my comment above. Lots more to do: * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs (copy step, validation step, ide-config.properties update step) > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24519 at 6/29/17 4:59 PM: ------------------------------------------------------------- TODOs: * migrate jboss.discovery.site.integration-stack-sap.url to jboss.fuse.extras.site.url in ide-config.properties: DONE * update jbosstools-fuse to use new property: see PR https://github.com/jbosstools/jbosstools-fuse/pull/986 DONE * update integration-stack to remove old properties: see PR https://github.com/jbosstools/jbosstools-integration-stack/pull/521 DONE * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs (copy step, validation step, ide-config.properties update step) ** staging copy step: DONE [0][1] ** validation step: DONE ** ide-config update: DONE ** release copy step: DONE [2][3][4] ** validation step: DONE ** ide-config update: DONE [0] http://download.jboss.org/jbosstools/oxygen/staging/updates/fuse-extras/4... [1] https://devstudio.redhat.com/11/staging/updates/fuse-extras/11.0.0.AM1d/ [2] http://download.jboss.org/jbosstools/oxygen/development/updates/fuse-extras/ [3] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... [4] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... was (Author: nickboldt): TODOs: * migrate jboss.discovery.site.integration-stack-sap.url to jboss.fuse.extras.site.url in ide-config.properties: DONE * update jbosstools-fuse to use new property: see PR https://github.com/jbosstools/jbosstools-fuse/pull/986 DONE * update integration-stack to remove old properties: see PR https://github.com/jbosstools/jbosstools-integration-stack/pull/521 DONE * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs (copy step, validation step, ide-config.properties update step) ** staging copy step: DONE [0][1] ** validation step: ** ide-config update: DONE ** release copy step: DONE [2][3][4] ** validation step: ** ide-config update: DONE [0] http://download.jboss.org/jbosstools/oxygen/staging/updates/fuse-extras/4... [1] https://devstudio.redhat.com/11/staging/updates/fuse-extras/11.0.0.AM1d/ [2] http://download.jboss.org/jbosstools/oxygen/development/updates/fuse-extras/ [3] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... [4] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24519) Ensure SAP tooling is available from within JBT/devstudio

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24519?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-24519 at 6/29/17 4:38 PM: ------------------------------------------------------------- TODOs: * migrate jboss.discovery.site.integration-stack-sap.url to jboss.fuse.extras.site.url in ide-config.properties: DONE * update jbosstools-fuse to use new property: see PR https://github.com/jbosstools/jbosstools-fuse/pull/986 DONE * update integration-stack to remove old properties: see PR https://github.com/jbosstools/jbosstools-integration-stack/pull/521 DONE * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs (copy step, validation step, ide-config.properties update step) ** staging copy step: DONE [0][1] ** validation step: ** ide-config update: DONE ** release copy step: DONE [2][3][4] ** validation step: ** ide-config update: DONE [0] http://download.jboss.org/jbosstools/oxygen/staging/updates/fuse-extras/4... [1] https://devstudio.redhat.com/11/staging/updates/fuse-extras/11.0.0.AM1d/ [2] http://download.jboss.org/jbosstools/oxygen/development/updates/fuse-extras/ [3] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... [4] http://download.jboss.org/jbosstools/static/oxygen/development/updates/fu... was (Author: nickboldt): TODOs: * migrate jboss.discovery.site.integration-stack-sap.url to jboss.fuse.extras.site.url in ide-config.properties: DONE * update jbosstools-fuse to use new property: see PR https://github.com/jbosstools/jbosstools-fuse/pull/986 DONE * update integration-stack to remove old properties: see PR https://github.com/jbosstools/jbosstools-integration-stack/pull/521 DONE * ensure license / readme are up to date in the github repo * integrate publishing of fuse-extras site into staging & release jobs (copy step, validation step, ide-config.properties update step) ** staging copy step: DONE ** validation step: ** ide-config update: DONE ** release copy step: ** validation step: ** ide-config update: DONE > Ensure SAP tooling is available from within JBT/devstudio > ---------------------------------------------------------- > > Key: JBIDE-24519 > URL: https://issues.jboss.org/browse/JBIDE-24519 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, fuse-tooling > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.AM2 > > > Need to make sure that whatever magic happens today in the IS for supporting the SAP Tooling gets migrated to JBT/devstudio. > {quote} > Github = https://github.com/jbosstools/jbosstools-fuse-extras > CCI PR Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > CCI Update SIte Build: https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/FuseToo... > Update Site CI: http://download.jboss.org/jbosstools/oxygen/snapshots/builds/jbosstools-f... > SAP data layer: http://fuse-sap.mw.lab.eng.bos.redhat.com/repositories/fuse-sap-data-laye... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4452) For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4452?page=com.atlassian.jira.plugin.... ] Nick Boldt reassigned JBDS-4452: -------------------------------- Assignee: Jeff MAURY > For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4452 > URL: https://issues.jboss.org/browse/JBDS-4452 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.0.0.AM2 > > > For JBDS 11.0.0.AM2 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.AM2-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.AM2-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4452) For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4452?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4452: ---------------------------------- bump up to parent pom version = 4.5.0.AM2-SNAPSHOT > For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4452 > URL: https://issues.jboss.org/browse/JBDS-4452 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.0.0.AM2 > > > For JBDS 11.0.0.AM2 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.AM2-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.AM2-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4452) For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4452?page=com.atlassian.jira.plugin.... ] Nick Boldt closed JBDS-4452. ---------------------------- Resolution: Done > For JBDS 11.0.0.AM2: Prepare for 4.5.0.AM2 / 11.0.0.AM2 [installer] > ------------------------------------------------------------------- > > Key: JBDS-4452 > URL: https://issues.jboss.org/browse/JBDS-4452 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 11.0.0.AM2 > > > For JBDS 11.0.0.AM2 [installer]: Please perform the following tasks: > > 1. Check out your existing *{color:orange}master{color}* branch: > > {code} > git checkout master > {code} > > 2. Update your *{color:orange}master branch{color}* root pom to use the latest parent pom version, *{color:orange}4.5.0.AM2-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.AM2-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.AM2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch > > 3. Ensure that component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. > > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.26.0:set-version -DnewVersion=1.0.1-SNAPSHOT > {code} > > > 4a. Ensure you've *built your code* using the latest *minimum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.0.AM1-SNAPSHOT > > {code} > mvn clean verify -Dtpc.version=4.70.0.AM1-SNAPSHOT > {code} > > 5. Close (do not resolve) this JIRA when done. > > 6. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE...] to do, please complete them next. > > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for installer task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- 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