August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24867) Remove dependency on private git repos in tests

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24867: ------------------------------------- Summary: Remove dependency on private git repos in tests Key: JBIDE-24867 URL: https://issues.jboss.org/browse/JBIDE-24867 Project: Tools (JBoss Tools) Issue Type: Task Components: integration-tests, openshift Affects Versions: 4.5.0.Final Reporter: Josef Kopriva -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Lars Heinemann commented on JBIDE-24866: ---------------------------------------- I prepared a PR for the version bump at https://github.com/jbosstools/jbosstools-fuse-extras/pull/72. We can merge it after 24 hours. > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools-extras]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM1-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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4506) Fuse tools configuration fails to install from bundled installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4506?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4506: ------------------------------------- This is the case only for bundle installer and I updated summary accordingly. > Fuse tools configuration fails to install from bundled installer > ---------------------------------------------------------------- > > Key: JBDS-4506 > URL: https://issues.jboss.org/browse/JBDS-4506 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 11.0.0.GA > > > Apparently, the fusetools requirement doesn't get updated in GA build. The installer file name is mismatched, which causes a wrong path for fuse installation. And version is stuck at AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4506) Fuse tools configuration fails to install from bundled installer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4506?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4506: -------------------------------- Summary: Fuse tools configuration fails to install from bundled installer (was: Fuse tools configuration does not match devstudio's and fails to install) > Fuse tools configuration fails to install from bundled installer > ---------------------------------------------------------------- > > Key: JBDS-4506 > URL: https://issues.jboss.org/browse/JBDS-4506 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 11.0.0.GA > > > Apparently, the fusetools requirement doesn't get updated in GA build. The installer file name is mismatched, which causes a wrong path for fuse installation. And version is stuck at AM1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24854) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24854?page=com.atlassian.jira.plugi... ] Lars Heinemann edited comment on JBIDE-24854 at 8/11/17 1:39 AM: ----------------------------------------------------------------- Jenkins still is configured for 4.70.0.AM1-SNAPSHOT (remember we are still on Fuse CI) was (Author: lhein): Jenkins still is configured for 4.70.0.AM1-SNAPSHOT > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools] > ------------------------------------------------------------------- > > Key: JBIDE-24854 > URL: https://issues.jboss.org/browse/JBIDE-24854 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM1-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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Lars Heinemann edited comment on JBIDE-24866 at 8/11/17 1:39 AM: ----------------------------------------------------------------- Version wasn't bumped to 10.1.0 in Jenkins and also not in codebase was (Author: lhein): Version wasn't bumped to 10.1.0 in Jenkins > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools-extras]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM1-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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24866) For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras]

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24866?page=com.atlassian.jira.plugi... ] Lars Heinemann edited comment on JBIDE-24866 at 8/11/17 1:21 AM: ----------------------------------------------------------------- Version wasn't bumped to 10.1.0 in Jenkins was (Author: lhein): Version wasn't bumped to 10.1.0 > For JBIDE 4.5.1.AM1: Prepare for 4.5.1.AM1 / 11.1.0.AM1 [fusetools-extras] > -------------------------------------------------------------------------- > > Key: JBIDE-24866 > URL: https://issues.jboss.org/browse/JBIDE-24866 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools-extras > Reporter: Nick Boldt > Assignee: Lars Heinemann > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM1 > > > For JBIDE 4.5.1.AM1 [fusetools-extras]: 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.1.AM1-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.1.AM1-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.1.AM1-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.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {code} > > 4b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.70.2.Final > > {code} > mvn clean verify -Dtpc.version=4.70.2.Final > {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 fusetools-extras 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4404) DevSuite 1.4 Installer hung during install waiting for cygwin

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4404?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4404: -------------------------------- Fix Version/s: 11.x (was: 11.0.0.GA) > DevSuite 1.4 Installer hung during install waiting for cygwin > ------------------------------------------------------------- > > Key: JBDS-4404 > URL: https://issues.jboss.org/browse/JBDS-4404 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Environment: Windows 10 Pro/64, DevSuite 1.4 installer > Reporter: Robert Terzi > Assignee: Denis Golovin > Fix For: 11.x > > Attachments: cygwin-failed-installer-hung.png, install.log, install.log, install.log > > > Attempting to install DevSuite 1.4 never completed, got stuck on waiting for Cygwin. > Attaching C:\DevelopmentSuite\installer.log, but it doesn't seem like it's got the info. Some of the last messages are Dev Studio installed correctly. > Cygwin was previously installed in C:\cygwin but not detected by installer so was installing it's own copy in \DevelopmentSuite. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24765) implement workaround for blocked branches when we need to update parent poms automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24765?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-24765: ------------------------------------ Found a solution: * make me an admin, and * uncheck the box for "Include Administrators" on https://github.com/jbosstools/jbosstools-<project>/settings/branches/master I verified this works here: * https://github.com/jbosstools/jbosstools-fuse/commits/master -> https://github.com/jbosstools/jbosstools-fuse/commit/43541327311a820bf5ed... * https://github.com/jbosstools/jbosstools-fuse-extras/commits/master -> https://github.com/jbosstools/jbosstools-fuse-extras/commit/704177d6a1c8c... > implement workaround for blocked branches when we need to update parent poms automatically > ------------------------------------------------------------------------------------------ > > Key: JBIDE-24765 > URL: https://issues.jboss.org/browse/JBIDE-24765 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Once protected branches are implemented, branching/tagging & simple root pom updates may not be possible w/o a review. > So, we need to implement an automated workflow that looks like this: > * submit a PR, then > * script a review (by a different user), then > * merge the PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24765) implement workaround for blocked branches when we need to update parent poms automatically

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24765?page=com.atlassian.jira.plugi... ] Nick Boldt resolved JBIDE-24765. -------------------------------- Resolution: Done > implement workaround for blocked branches when we need to update parent poms automatically > ------------------------------------------------------------------------------------------ > > Key: JBIDE-24765 > URL: https://issues.jboss.org/browse/JBIDE-24765 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build > Affects Versions: 4.5.1.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.1.AM1 > > > Once protected branches are implemented, branching/tagging & simple root pom updates may not be possible w/o a review. > So, we need to implement an automated workflow that looks like this: > * submit a PR, then > * script a review (by a different user), then > * merge the PR -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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