September 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-4528) Fix download size value in bytes for components

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-4528?page=com.atlassian.jira.plugin.... ] Mohit Suman reassigned JBDS-4528: --------------------------------- Assignee: Mohit Suman > Fix download size value in bytes for components > ----------------------------------------------- > > Key: JBDS-4528 > URL: https://issues.jboss.org/browse/JBDS-4528 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 11.1.0.AM1 > Reporter: Mohit Suman > Assignee: Mohit Suman > > The product download size value to be updated and stored in bytes(binary). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4528) Fix download size value in bytes for components

by Mohit Suman (JIRA)

Mohit Suman created JBDS-4528: --------------------------------- Summary: Fix download size value in bytes for components Key: JBDS-4528 URL: https://issues.jboss.org/browse/JBDS-4528 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 11.1.0.AM1 Reporter: Mohit Suman The product download size value to be updated and stored in bytes(binary). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-24797: ------------------------------------------ I found the maven plugin, that allows to apply formatting exported from Eclipse preferences: http://code.revelc.net/formatter-maven-plugin/formatter-maven-plugin/. I also created 2 PRs to jbosstools-openshift # https://github.com/jbosstools/jbosstools-openshift/pull/1560 - slightly changed eclipse formatter # https://github.com/jbosstools/jbosstools-openshift/pull/1559 - default eclipse formatter You can find all the details in the PR comment. > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.1.AM2 > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:50 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up and terminates once you have it continue after the breakpoint (F8). So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:50 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother, it keeps waiting. But then the debug session in Eclipse gives up. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:41 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external (Chrome MacOS) browser doesnt seem to bother. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external browser doesnt seem to bother. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-24868 at 9/1/17 10:39 AM: ------------------------------------------------------------------- [~aurelien.pupier] [~rhuss] Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. The external browser doesnt seem to bother. So we should make sure that we respect the preferences where the user chooses to use an internal or external browser and go for this, agree? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 was (Author: adietish): Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. Still an improvement, isnt it? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24868) Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24868?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-24868: ------------------------------------------ Setting the router timeout via the annotation described above works for me. The router wont timeout any more and there's no "504 Gateway timeout" error being displayed any more. But then the Eclipse browser gives up, saying that the page could not be loaded. Still an improvement, isnt it? * Without timeout setting in the router, default 1 minute timeout applies: Browser displays 504 Gateway timeout after a minute https://youtu.be/J6pmzVBgbnk * AnnotatingWithout timeout setting in the router, default 1 minute timeout applies: Internal Eclipse browser pops up a dialog saying that it could not load the page. My external chrome didnt come up with such a message, it just kept waiting for several minutes (didnt wait until the end): https://youtu.be/KzxDvgm5kF4 > Server adapter: Switch off pod livenessProbe.periodSecond property and router timeout during debug session > ---------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24868 > URL: https://issues.jboss.org/browse/JBIDE-24868 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.0.Final > Reporter: Aurélien Pupier > Assignee: Andre Dietisheim > Labels: openshift_v3, server_adapter > Fix For: 4.5.1.AM2 > > Attachments: breakpoint-suspend-thread.png > > > it will avoid to have "debug connections always killed after 30s staying in a breakpoint" > see https://twitter.com/ro14nd/status/895886024387067904 for source of suggestion > k8 documentations on the matter are here: https://kubernetes.io/docs/tasks/configure-pod-container/configure-livene... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-24960: ---------------------------------- Assignee: Jeff MAURY > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Assignee: Jeff MAURY > Fix For: 4.5.1.AM3 > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24963) Create CDI 2 integration tests

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-24963: ------------------------------------ Summary: Create CDI 2 integration tests Key: JBIDE-24963 URL: https://issues.jboss.org/browse/JBIDE-24963 Project: Tools (JBoss Tools) Issue Type: Task Components: cdi, integration-tests Affects Versions: 4.5.1.AM2 Reporter: Lukáš Valach Assignee: Lukáš Valach Fix For: 4.5.1.AM3 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

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