February 2016 - jbosstools-issues

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-705: ---------------------------------------- [~mhusnain], ok, thanks. {quote} I decided to remove the resolution in (done) because known issues should be issues that are still open and (done) should be resolved issues. {quote} Let me try to explain again: The goal has always been that the query should return known issues at the time of the release. Not at the time of entering the query into JIRA, which may be much much later. So that's the reason why resolution (done) makes sense in this context. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Misha Ali commented on TOOLSDOC-705: ------------------------------------ Hi [~mmalina]. 1. Agreed on the Resolves issues. I'll make this change first thing tomorrow. 2. For Known Issues, when fiddling with the query, I decided to remove the resolution in (done) because known issues should be issues that are still open and (done) should be resolved issues. I'm happy to accept your amended version of the query so I'll test it and add it to the release notes tomorrow as well and then flag you here to have a final look for approval. > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout of starting CDK should be longer by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21622: ---------------------------------- Summary: Timeout of starting CDK should be longer by default (was: Timeout to stop starting of CDK should be longer by default) > Timeout of starting CDK should be longer by default > --------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout to stop starting of CDK should be longer by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21622: ---------------------------------- Description: When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. !cdk_vagrant_halt.png! was: When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. Timeout could be higher by default. !cdk_vagrant_halt.png! > Timeout to stop starting of CDK should be longer by default > ----------------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. Timeout should be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Martin Malina commented on TOOLSDOC-705: ---------------------------------------- Hi [~mhusnain], I have comments about the queries. 4.1. Resolved Issues The query you include shows 64 issues total: {code} (project in (JBDS) AND affectedVersion <= 9.1.0.Beta2 AND fixVersion in (9.1.0.Beta2)) OR (project in (JBIDE) AND affectedVersion <= 4.3.1.Beta2 AND fixVersion in (4.3.1.Beta2)) AND type in (Bug) AND resolution in (Done) {code} I wonder why we have the affectedVersion there. Do you know? Without it, we have 75 issues. I think the idea was to exclude issues that never appeared in a previous versions - for example when there is a new functionality in Beta2 and there is a bug recognized right away and fixed still in Beta2 before anybody had a chance to even see this bug. But on the other hand, this also misses issues without affectedVersion set at all which in this case is 7 issues out of those 75. So I think it's better to remove the affectedVersion constraints there. 4.2. Known Issues You decided to remove "OR resolution in (Done)", but there was a reason for that. There were two parts of the query - the first part was bugs, that are still open at the time of the search - in the past we limited this only to bugs with older affectedVersion because newer bugs might not be relevant. But I'm fine with removing this. The second part is bugs, that are already resolved at the time of the search, but were fixed later on, so for this release, they were present. For example let's say it is March and JBDS 9.1.0.GA is already out. You decide to check Beta2 Release Notes. And in the known issues query, you want to see which bugs were still present in Beta2. Let's say there is a bug JBDS-9999 that was fixed in 9.1.0.CR1. You still want to see this bug in Beta2 known issues query. That's why you have: resolution in (Done) AND fixVersion > "9.1.0.Beta2" - this was a bug that is now fixed, but was still present in Beta2. So I think this is still reasonable to have there. So I would suggest this query: {code} (project in (JBDS) AND (affectedVersion <= "9.1.0.Beta2" OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "9.1.0.Beta2") OR project in (JBIDE) AND (affectedVersion <= "4.3.1.Beta2" OR affectedVersion is EMPTY) AND (resolution in (Unresolved) OR resolution in (Done) AND fixVersion > "4.3.1.Beta2")) AND type in (Bug) {code} I believe this is the last query that you suggested before you dropped the resolved jiras from the query. What do you think? > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Martin Malina > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-705) JBDS 9.1 Beta2: Release Notes

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-705?page=com.atlassian.jira.plug... ] Martin Malina reassigned TOOLSDOC-705: -------------------------------------- Assignee: Misha Ali (was: Martin Malina) > JBDS 9.1 Beta2: Release Notes > ----------------------------- > > Key: TOOLSDOC-705 > URL: https://issues.jboss.org/browse/TOOLSDOC-705 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Reporter: Misha Ali > Assignee: Misha Ali > > Create new Beta2 release notes, fix the script and update the relevant details. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout to stop starting of CDK should be longer by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21622: ---------------------------------- Summary: Timeout to stop starting of CDK should be longer by default (was: Timeout to stop starting of CDK should be longer) > Timeout to stop starting of CDK should be longer by default > ----------------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. Timeout could be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) Timeout to stop starting of CDK should be longer by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21622: ---------------------------------- Priority: Major (was: Critical) > Timeout to stop starting of CDK should be longer by default > ----------------------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. Timeout could be higher by default. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) CDK server adapter is halted after 450 seconds

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21622: ------------------------------------- Summary: CDK server adapter is halted after 450 seconds Key: JBIDE-21622 URL: https://issues.jboss.org/browse/JBIDE-21622 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Attachments: cdk_vagrant_halt.png When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21622) CDK server adapter is halted after 450 seconds

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21622?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21622: ---------------------------------- Priority: Critical (was: Major) > CDK server adapter is halted after 450 seconds > ---------------------------------------------- > > Key: JBIDE-21622 > URL: https://issues.jboss.org/browse/JBIDE-21622 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Attachments: cdk_vagrant_halt.png > > > When I am creating a new CDK adapter in tooling, it is stopped after 450 second. Although there were no errors. My creating and starting of CDK took so long because it was downloading CDK image really slow. I think it is not proper to kill it (vagrant halt) after 450 seconds just like that. > !cdk_vagrant_halt.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 February 2016