March 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19470) Upgrade Forge Runtime to 2.15.2.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19470?page=com.atlassian.jira.plugi... ] Pavol Srna commented on JBIDE-19470: ------------------------------------ I've opened https://issues.jboss.org/browse/JBIDE-19540 to track the version problems. > Upgrade Forge Runtime to 2.15.2.Final > ------------------------------------- > > Key: JBIDE-19470 > URL: https://issues.jboss.org/browse/JBIDE-19470 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Final, 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19470) Upgrade Forge Runtime to 2.15.2.Final

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19470?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-19470. ------------------------------ Verified in JBT 4.2.3.Final build. > Upgrade Forge Runtime to 2.15.2.Final > ------------------------------------- > > Key: JBIDE-19470 > URL: https://issues.jboss.org/browse/JBIDE-19470 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.2.3.CR1 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.2.3.Final, 4.3.0.Alpha2 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19540) Forge runtime version is not aligned with its eclipse plugin version

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19540?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19540: ------------------------------- Fix Version/s: (was: 4.2.3.Final) > Forge runtime version is not aligned with its eclipse plugin version > -------------------------------------------------------------------- > > Key: JBIDE-19540 > URL: https://issues.jboss.org/browse/JBIDE-19540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Pavol Srna > > Forge 2 runtime included with JBDS 8.1.0.CR1 is 2.15.1 and for JBDS 8.1.0.GA it's 2.15.2, but in both cases the plugin version is org.jboss.tools.forge2.runtime_2.15.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19540) Forge runtime version is not aligned with its eclipse plugin version

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19540?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-19540: ------------------------------- Fix Version/s: 4.2.3.Final > Forge runtime version is not aligned with its eclipse plugin version > -------------------------------------------------------------------- > > Key: JBIDE-19540 > URL: https://issues.jboss.org/browse/JBIDE-19540 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.3.Final > Reporter: Pavol Srna > Fix For: 4.2.3.Final > > > Forge 2 runtime included with JBDS 8.1.0.CR1 is 2.15.1 and for JBDS 8.1.0.GA it's 2.15.2, but in both cases the plugin version is org.jboss.tools.forge2.runtime_2.15.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19540) Forge runtime version is not aligned with its eclipse plugin version

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-19540: ---------------------------------- Summary: Forge runtime version is not aligned with its eclipse plugin version Key: JBIDE-19540 URL: https://issues.jboss.org/browse/JBIDE-19540 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.2.3.Final Reporter: Pavol Srna Forge 2 runtime included with JBDS 8.1.0.CR1 is 2.15.1 and for JBDS 8.1.0.GA it's 2.15.2, but in both cases the plugin version is org.jboss.tools.forge2.runtime_2.15.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-622) QE Review: JBDS 8.1 GA Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-622?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-622: ---------------------------------------- Based on our discussion on IRC, I suggest we use this for Known Issues: {code} (project in (JBDS) AND affectedVersion >= "7.0.0.GA" AND affectedVersion <= "8.1.0.GA" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "8.1.0.GA") OR project in (JBIDE) AND affectedVersion >= "4.1.0.Final" AND affectedVersion <= "4.2.3.Final" AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.2.3.Final")) AND type in (Bug) {code} As described in the JIRA, the problem with the above query is that it also returns JIRAs that have multiple fixVersion, such as JBIDE-19377 - this JIRA is fixed in both 4.2.3.x and 4.3.x, so it's already fixed in JBDS 8.0.0.GA. But even if we filtered these out, there would still be a number of JIRAs that were cloned for the second version - one jira for 4.2.x and one for 4.3. So this query would still show a jira that was fixed in e.g. 4.3.0.Alpha1 as a known issue in 4.2.3.Final even though there might be a second (cloned) jira with the same fix for 4.2.3.x. At this point I'm not sure what we can do other then going one by one in the list of jiras and manually selecting the ones that are relevant and then include them in the release notes directly. In any case, we concluded that it's too late to fix this for this release, so this will have to be looked at for next time. > QE Review: JBDS 8.1 GA Release Notes > ------------------------------------ > > Key: TOOLSDOC-622 > URL: https://issues.jboss.org/browse/TOOLSDOC-622 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > Need QE review of the following changes here: > http://docbuilder.usersys.redhat.com/23017/ > Changes: > * Updated queries for known and resolved issues > * Added cases to known issues -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19539) Create and use Mars M6 target-platform

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19539: -------------------------------------- Summary: Create and use Mars M6 target-platform Key: JBIDE-19539 URL: https://issues.jboss.org/browse/JBIDE-19539 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: target-platform Reporter: Mickael Istria Priority: Critical Mars M6 was released and contains interesting changes (in Platform UI), important version updates (EGit 4.0 and TM 4.0). We need to start using it ASAP to leverage new functionalities and adapt to the most important changes. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-622) QE Review: JBDS 8.1 GA Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-622?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-622: ------------------------------------ Hi Martin, I'll have a look at the staging server in a second and highlight the difference. The CR1 release notes are still available here internally: http://docbuilder.usersys.redhat.com/23055/ I requested that they be taken down because we will publish the new GA versions of the documents and the Release Notes in a few hours for GA and the mechanism requires that the old release notes (which are a different package due to the CR1 in the title) must be removed or all the new documentation appears under 8.1 Beta. As part of the dependency for release, we have to remove them first, then tag the new docs and then refresh the stage, in that order. Each of these steps needs at 1-3 hours to automatically update, so I've requested the CR1 Release Notes removed a few hours ahead of time from the Customer Service Portal. > QE Review: JBDS 8.1 GA Release Notes > ------------------------------------ > > Key: TOOLSDOC-622 > URL: https://issues.jboss.org/browse/TOOLSDOC-622 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Sub-task > Components: Release Notes > Affects Versions: 4.2.3.Final > Reporter: Misha Ali > Assignee: Misha Ali > Fix For: 4.2.3.Final > > > Need QE review of the following changes here: > http://docbuilder.usersys.redhat.com/23017/ > Changes: > * Updated queries for known and resolved issues > * Added cases to known issues -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19538) Unit test failure: ConnectionTest.testGetHost is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19538?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19538: ------------------------------------------ jenkins build https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift... is back to stable :) {code} Results : Tests run: 84, Failures: 0, Errors: 0, Skipped: 0 [INFO] All tests passed! [INFO] [INFO] --- repository-utils:0.22.1-SNAPSHOT:compare-version-with-baselines (default) @ org.jboss.tools.openshift.test --- [INFO] ------------------------------------------------------------------------ [INFO] Reactor Summary: [INFO] [INFO] openshift.tests .................................... SUCCESS [ 0.560 s] [INFO] org.jboss.tools.openshift.egit.test ................ SUCCESS [ 23.130 s] [INFO] org.jboss.tools.openshift.express.test ............. SUCCESS [ 17.171 s] [INFO] org.jboss.tools.openshift.test ..................... SUCCESS [ 13.176 s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS [INFO] ------------------------------------------------------------------------ [INFO] Total time: 01:13 min [INFO] Finished at: 2015-03-31T04:26:39-04:00 [INFO] Final Memory: 59M/643M [INFO] ------------------------------------------------------------------------ {code} > Unit test failure: ConnectionTest.testGetHost is failing > -------------------------------------------------------- > > Key: JBIDE-19538 > URL: https://issues.jboss.org/browse/JBIDE-19538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > In jenkins (http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_...) there's a failing unit test which makes jenkins build unstable: > {code} > Failed tests: > ConnectionTest.testGetHost:58 expected:<[localhost]> but was:<[https://localhost:8433]> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19538) Unit test failure: ConnectionTest.testGetHost is failing

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19538?page=com.atlassian.jira.plugi... ] Andre Dietisheim closed JBIDE-19538. ------------------------------------ > Unit test failure: ConnectionTest.testGetHost is failing > -------------------------------------------------------- > > Key: JBIDE-19538 > URL: https://issues.jboss.org/browse/JBIDE-19538 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.0.Alpha2 > > > In jenkins (http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_...) there's a failing unit test which makes jenkins build unstable: > {code} > Failed tests: > ConnectionTest.testGetHost:58 expected:<[localhost]> but was:<[https://localhost:8433]> > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 11 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 March 2015