July 2017 - jbosstools-issues - Jboss List Archives

[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.x (was: 11.0.0.AM2) > 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.x > > > 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] (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 updated JBDS-3893: ----------------------------- Fix Version/s: 11.x (was: 11.0.0.AM2) > 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.x > > > 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-24689) For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools]

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24689?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-24689: ----------------------------------------- failing test fixed with this commit: https://github.com/jbosstools/jbosstools-fuse/pull/1014/commits/94d1438bf... will need to investigate if there is not an issue with the JMX connections > For JBIDE 4.5.0.Final: Prepare for 4.5.0.Final / 11.0.0.GA [fusetools] > ---------------------------------------------------------------------- > > Key: JBIDE-24689 > URL: https://issues.jboss.org/browse/JBIDE-24689 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: fusetools > Reporter: Nick Boldt > Assignee: Aurélien Pupier > Priority: Blocker > Labels: task > Fix For: 4.5.0.Final > > > For JBIDE 4.5.0.Final [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.0.Final-SNAPSHOT{color}*: > > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.5.0.Final-SNAPSHOT</version> > </parent> > {code} > > Now, your root pom will use parent pom version: > > * *{color:orange}4.5.0.Final-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 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4454) Path to JDK needs to be updated after every update of JDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4454?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4454: ----------------------------- Sprint: devex #135 July 2017 > Path to JDK needs to be updated after every update of JDK > --------------------------------------------------------- > > Key: JBDS-4454 > URL: https://issues.jboss.org/browse/JBDS-4454 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: build, installer > Affects Versions: 11.0.0.AM1 > Environment: Fedora 26 > Reporter: Josef Kopriva > Assignee: Nick Boldt > Fix For: 11.0.0.AM2 > > Attachments: image-2017-06-30-11-01-40-783.png, screenshot-1.png > > > After every update of JDK, path to JDK in file devstudio.ini needs to be updated. This does not happening in Eclipse. > !image-2017-06-30-11-01-40-783.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4426) Devstudio 11 includes link to devstudio 10 to install features, which it should not

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4426?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4426: ----------------------------- Sprint: devex #135 July 2017 > Devstudio 11 includes link to devstudio 10 to install features, which it should not > ----------------------------------------------------------------------------------- > > Key: JBDS-4426 > URL: https://issues.jboss.org/browse/JBDS-4426 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, central-update, updatesite > Affects Versions: 11.0.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 11.0.0.AM2 > > Attachments: devstudio-10-in-11.png > > > OOTB the BYOE installation of Devstudio 11.0.0.AM1 contains a link to devstudio 10's stable update site. It should NOT have this link. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24518) change github check frequency for CI builds from 8hrs to 20 mins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24518?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24518: ------------------------------- Sprint: devex #132 May 2017, devex #135 July 2017 (was: devex #132 May 2017) > change github check frequency for CI builds from 8hrs to 20 mins > ---------------------------------------------------------------- > > Key: JBIDE-24518 > URL: https://issues.jboss.org/browse/JBIDE-24518 > 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.AM2 > > > Currently the jbosstools-* component project builds run every 8hrs, with a nightly buildflow also triggering a rebuild. But since breaking changes are frequently NOT fixed quickly enough as devs cannot or will not kick their own builds, we need to implement a better strategy to check github for changes more often. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Sprint: devex #132 May 2017, devex #135 July 2017 (was: devex #132 May 2017) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24673) install tests (central, EA) are broken and failing

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24673?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24673: ------------------------------- Sprint: devex #135 July 2017 > install tests (central, EA) are broken and failing > --------------------------------------------------- > > Key: JBIDE-24673 > URL: https://issues.jboss.org/browse/JBIDE-24673 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, central-update, updatesite > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > Checking these test jobs, I see they've been red for a while but no one has noticed. > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud... > So, a few things need to be done here: > a) make the tests pass > b) ensure emails are sent for unexpected failures to jbosstools-dev, nboldt, jmaury -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24674) update the list of nag emails to send on QE stage day

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24674?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24674: ------------------------------- Sprint: devex #135 July 2017 > update the list of nag emails to send on QE stage day > ----------------------------------------------------- > > Key: JBIDE-24674 > URL: https://issues.jboss.org/browse/JBIDE-24674 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.5.0.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.0.Final > > > We should send nag emails re: sprint triage when pushing QE stage build to remind people to move their issues to the next sprint, or resolve them. > We should also send a nag email to Jeff to create the new sprint versions in JIRA so that triage can actually occur, or else people won't be able to assign existing (slipped) issues to the forthcoming sprint. > And, we should fire the jiralint-weekly to spam people w/ reminders of which JIRAs are unresolved for the code-frozen version. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4448) JBDS install failure with no explanation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4448?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4448: -------------------------------- Story Points: 3 > JBDS install failure with no explanation > ----------------------------------------- > > Key: JBDS-4448 > URL: https://issues.jboss.org/browse/JBDS-4448 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.4.0.GA > Environment: Mac, using DevSuite installer 1.4.1 GA > Reporter: Bob Davis > Assignee: Denis Golovin > Priority: Critical > Attachments: Screen Shot 2017-06-26 at 2.09.01 PM.png, install.log > > > Installing RED HAT JBOSS DEVELOPER STUDIO10.4.0.GA failed, and no explanation or remediation such as "try again" or "remove ...", etc. was offered. The end user is stuck with no way out. > Additionally, the "next step" displayed is "Get Started", but there is no way to get there, no button to "Next", or any indication of how to move forward to it. > Quitting is the only option. -- 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