August 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-24749) Rename cdk runtime detector to cdk 2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24749?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-24749. --------------------------------- Verified in devstudio-11.0.0.GA-v20170804-2000-B708-installer-standalone.jar . Now the cdk 2 detector includes 2.x at the end. > Rename cdk runtime detector to cdk 2 > ------------------------------------ > > Key: JBIDE-24749 > URL: https://issues.jboss.org/browse/JBIDE-24749 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-detection > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: runtime-detectors.png > > > In JBIDE-24584 I requested that cdk server adapter be renamed to cdk 2 which is now done. But today I noticed that we missed the runtime detector: > Go to Preferences -> JBoss Tools -> JBoss Runtime Detection > On that page, there is a table called Available runtime detectors which, among others, includes: > Container Development Environment 3 > Container Development Environment > !runtime-detectors.png! > So the latter should be renamed to include "2" or "2.x" - probably the latter to be consistent with the server adapter name. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24770) Loading service-manager status shows up when starting cdk3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24770?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-24770: --------------------------------------- I think I already saw it fixed. [~odockal] will confirm. > Loading service-manager status shows up when starting cdk3 > ---------------------------------------------------------- > > Key: JBIDE-24770 > URL: https://issues.jboss.org/browse/JBIDE-24770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.0.Final > > Attachments: service-manager.png > > > During startup of cdk 3 server adapter, I get this in the status bar: > Loading service-manager... > !service-manager.png! > There is no service-manager in cdk 3. > I asked Rob and he said perhaps he forgot to rename a job. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20610) Request upstream enhancement to allow users more control over internet cache

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20610?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20610: --------------------------------------- I created a new issue to try and fix this problem from the other side (where we have control over it) - the server should not return no-cache for schema files: JBIDE-24801 > Request upstream enhancement to allow users more control over internet cache > ---------------------------------------------------------------------------- > > Key: JBIDE-20610 > URL: https://issues.jboss.org/browse/JBIDE-20610 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > The WTP internet cache preference page could / should include options where the user can customize cache duration or aggressively cache even if the no-cache header is set. > Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=475763 upstream is opened to track this issue -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24801) Remove no-cache header for xml schema files

by Martin Malina (JIRA)

Martin Malina created JBIDE-24801: ------------------------------------- Summary: Remove no-cache header for xml schema files Key: JBIDE-24801 URL: https://issues.jboss.org/browse/JBIDE-24801 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server, upstream Affects Versions: 4.5.0.Final Reporter: Martin Malina Assignee: Rob Stryker This is a followup of JBIDE-20610 . In the past we were trying to figure out how to make validation in Eclipse faster. The problem is that xml schema files return no-cache header and so Eclipse needs to fetch them over and over again. We tried to solve this on Eclipse side - allow ignoring of the no-cache http header. But why not try to solve this properly on the server side at least where we have control over it? I think there is no reason why request to urls like http://jboss.org/j2ee/dtd/service-ref_4_0.dtd should return no-cache. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20610) Request upstream enhancement to allow users more control over internet cache

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20610?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20610: --------------------------------------- So, I read through the BZ and this is how I understand the fix: 1. By default, no-cache header is still honored, so no caching happens there unless you check the checkbox in preferences 2. If you check the check-box, caching for no-cache will be 10 minutes 3. You can customize the default caching period, but this does not apply to the no-cache header On the BZ, Max previously commented on the suggestion that no-cache caching will be hard-coded to a few minutes: {quote} If the caching is only a few minutes this won't fix this problem. {quote} So this seems like not much was improved here :( I did check this in devstudio-11.0.0.GA-v20170804-2000-B708-installer-standalone.jar and it seems to work as expected. When I checked the ignore no-cache checkbox and then validated something, new entries were added to Cache entries. When I removed those entries and unchecked the checkbox and validated again, entries were not added. I didn't check the duration of the caching though. Cc: [~rawagner] > Request upstream enhancement to allow users more control over internet cache > ---------------------------------------------------------------------------- > > Key: JBIDE-20610 > URL: https://issues.jboss.org/browse/JBIDE-20610 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > The WTP internet cache preference page could / should include options where the user can customize cache duration or aggressively cache even if the no-cache header is set. > Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=475763 upstream is opened to track this issue -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20610) Request upstream enhancement to allow users more control over internet cache

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20610?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20610. --------------------------------- > Request upstream enhancement to allow users more control over internet cache > ---------------------------------------------------------------------------- > > Key: JBIDE-20610 > URL: https://issues.jboss.org/browse/JBIDE-20610 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.0.AM1 > > > The WTP internet cache preference page could / should include options where the user can customize cache duration or aggressively cache even if the no-cache header is set. > Bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=475763 upstream is opened to track this issue -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1156) Prepare Marketplace entry for Integration Stack 11.0.0.GA

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1156?page=com.atlassian.jira.plugin... ] Andrej Podhradsky commented on JBTIS-1156: ------------------------------------------ [~pleacu] is it necessary to list features in the categories? > Prepare Marketplace entry for Integration Stack 11.0.0.GA > --------------------------------------------------------- > > Key: JBTIS-1156 > URL: https://issues.jboss.org/browse/JBTIS-1156 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: distribution > Affects Versions: 11.0.0.CR2 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 11.0.0.GA > > > Prepare Marketplace entry for Integration Stack 11.0.0.GA. > [~pleacu] what categories will be available? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24717) OpenShift New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24717?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24717. ------------------------------ Resolution: Done > OpenShift New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24717 > URL: https://issues.jboss.org/browse/JBIDE-24717 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: cdk, openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Fix For: 4.5.0.Final > > > Andre Dietisheim, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed OpenShift JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for OpenShift, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for OpenShift by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24706 #comment Create N&N for OpenShift 4.5.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for OpenShift for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of OpenShift, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24711) Forge New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24711?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24711. ------------------------------ Resolution: Done > Forge New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24711 > URL: https://issues.jboss.org/browse/JBIDE-24711 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: forge > Reporter: Jeff MAURY > Assignee: George Gastaldi > Priority: Critical > Fix For: 4.5.0.Final > > > George Gastaldi, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Forge JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Forge, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Forge by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24706 #comment Create N&N for Forge 4.5.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Forge for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Forge, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24709) Docker New and Noteworthy for 4.5.0.Final

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24709?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-24709. ------------------------------ Resolution: Done > Docker New and Noteworthy for 4.5.0.Final > ----------------------------------------------------- > > Key: JBIDE-24709 > URL: https://issues.jboss.org/browse/JBIDE-24709 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: docker > Reporter: Jeff MAURY > Assignee: Jeff Johnston > Priority: Critical > Fix For: 4.5.0.Final > > > Jeff Johnston, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Docker JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Docker, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Docker by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-24706 #comment Create N&N for Docker 4.5.0.Final #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Docker for this milestone, please *reject* and *close* this issue. > ---- > If there is nothing new or noteworthy for 4.5.0.Final since the AM3 release of Docker, please *reject* and *close* this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to _add a comment to the final document_ then submit a PR to create a separate <component>-news-4.5.0.Final.adoc file here: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > However, if you want to _replace all previous N&Ns by a *new* document_, then submit a PR to create a *new* <component>-news-4.5.0.Final.adoc file, adding: {code}page-include-previous: false{code}. -- 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 August 2017