November 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4179) DevStudio installer uses console installation instead of wizard

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4179?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-4179: ------------------------------------ Assignee: Denis Golovin Interesting... [~dgolovin] have you seen it before? > DevStudio installer uses console installation instead of wizard > --------------------------------------------------------------- > > Key: JBDS-4179 > URL: https://issues.jboss.org/browse/JBDS-4179 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.2.0.GA > Environment: openjdk version "1.8.0_102" > OpenJDK Runtime Environment (build 1.8.0_102-b14) > Reporter: Marián Labuda > Assignee: Denis Golovin > > I tried to install latest DevStudio (devstudio-10.2.0.GA-v20161116-0039-B6472-installer-standalone.jar) but when I run installation as usual, I get console installation - at first whole license text and prompt to 1) Accept, 2) Reject, 3) Redisplay. After that installation unpack files to home and I am not able to select destination. > This happens with older version of openjdk8. With latest available openjdk for fedora (1.8.0_111) it works. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-23184: ------------------------------------------ [~jeffmaury] yes, it is dependent on OS version, as it was discussed from the beginning on our Deep Dive meetings. It works only for 1.3 version. But there is no code responsible for retrieving the OS version, we just silently fail if this functionality is not supported. But [~mlabuda]'s question is different. It won't work for any version if the project is created outside of eclipse, because we won't know then changes of what we need to watch (see my explanation above). Jeff, or did i understand wrongly? > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov reassigned JBIDE-23494: ---------------------------------------- Assignee: Dmitrii Bocharov > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23438) Create New and Noteworthy for 4.4.2.AM3

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23438?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23438. --------------------------------- All underlying subtasks resolved and closed. Closing this one. > Create New and Noteworthy for 4.4.2.AM3 > --------------------------------------- > > Key: JBIDE-23438 > URL: https://issues.jboss.org/browse/JBIDE-23438 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Priority: Blocker > Fix For: 4.4.2.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23470: ------------------------------------------ We really should unit-test the WatchManager. It proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it: JBIDE-23494 > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.Final > > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23470) Server Adapter: stuck restarting in debug mode

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23470?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-23470 at 11/16/16 7:40 AM: -------------------------------------------------------------------- We really have to unit-test the WatchManager. It proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it: JBIDE-23494 was (Author: adietish): We really should unit-test the WatchManager. It proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it: JBIDE-23494 > Server Adapter: stuck restarting in debug mode > ---------------------------------------------- > > Key: JBIDE-23470 > URL: https://issues.jboss.org/browse/JBIDE-23470 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.2.Final > > Attachments: failed-to-detect-pod.png, server-adapter-stuck-starting.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23494: ---------------------------------------- Summary: Tests: Should provide unit-tests for WatchManager Key: JBIDE-23494 URL: https://issues.jboss.org/browse/JBIDE-23494 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.4.2.AM3 Reporter: Andre Dietisheim Priority: Critical WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23184) Add Capability to Watch Projects

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23184?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-23184: ------------------------------------ I'm in line with [~mlabuda] If a project gets added or deleted outside DevStudio, it should be reflected in DevStudio. That was my understanding of the issue. Now we should be clear that it is also dependent of the OpenShift version used, no ? > Add Capability to Watch Projects > -------------------------------- > > Key: JBIDE-23184 > URL: https://issues.jboss.org/browse/JBIDE-23184 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Jeff Cantrill > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM3 > > > Origin now allows watching of projects for adds and delete. Add capability to watch projects. Need to take into consideration how one might use the latest code against an older server version since older servers did not support project watch > $ curl -k -H "Authorization: Bearer LU3A1EyTOdnRhkLqe8Gqkgk850eTNlljz18NwLA-108" https://192.168.1.13:8443/oapi/v1/projects?watch=true&&resourceVersion= > {"type":"ADDED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","uid":"41f418fc-7ea3-11e6-803b-507b9dfa4ab3","resourceVersion":"942","creationTimestamp":"2016-09-19T19:57:13Z","annotations":{"openshift.io/description":"","openshift.io/display-name":"","openshift.io/requester":"developer","openshift.io/sa.scc.mcs":"s0:c7,c4","openshift.io/sa.scc.supplemental-groups":"1000050000/10000","openshift.io/sa.scc.uid-range":"1000050000/10000"}},"spec":{"finalizers":["openshift.io/origin","kubernetes"]},"status":{"phase":"Active"}}} > {"type":"DELETED","object":{"kind":"Project","apiVersion":"v1","metadata":{"name":"foo","selfLink":"/oapi/v1/projects/foo","creationTimestamp":null},"spec":{},"status":{}}} > openshift-origin PR that made it available: https://github.com/openshift/origin/pull/6828 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Supriya Bharadwaj commented on JBIDE-23213: ------------------------------------------- Thanks [~mmalina] for the update. - For mac OS, I guess we should rename the older versions too because as you said: apple started referring to the OS as macOS (previously OS X, previously Mac OS X), "even retrospectively". - For Fedora 25: I'll wait for this and confirm it with you once again after November 22 - Ubuntu 16.10: I'll wait for your confirmation on adding this > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23213) Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23213?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23213: --------------------------------------- Update: macOS is for sure: We should drop 10.10 and have 10.11 and 10.12 in the support matrix for devstudio 10.2. Please also note that since 10.12, apple started referring to the OS as macOS (previously OS X, previously Mac OS X), even retrospectively. I'm not sure what we want to do here, I'll leave it up to you - it would make sense to use macOS in the table for devstudio 10.2, but then won't it be ugly if the older versions say OS X in the same document? I'm not sure. Fedora 25 was supposed to be released on November 15, but apparently was postponed to November 22, so we don't know yet if we can include it or not - it will require some testing. https://fedoraproject.org/wiki/Releases/25/Schedule Ubuntu 16.10 is out already, so I will ask others who are using it if they know of an issue and then we can decide if we can add it. The result would be that we would support these two versions: 16.04.1 LTS and 16.10 > Update supported configuration docs / test plans / platforms for jbosstools 4.4.2 / devstudio 10.2 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23213 > URL: https://issues.jboss.org/browse/JBIDE-23213 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.Final > Reporter: Nick Boldt > Assignee: Martin Malina > Fix For: 4.4.2.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016. > [0] https://wiki.ubuntu.com/Releases > * Should we move to 16.04.1 LTS and 16.10? > * Should we move to 14.04.5 LTS and 16.04.1 LTS ? > * Should we move to 14.04.5 LTS and 16.10? > Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1]. > [1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... > But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right? > [2] https://fedoraproject.org/wiki/Releases/25/Schedule > * Should we move to F24 and F25? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 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 November 2016