February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-23636: --------------------------------------- [~jeffmaury], I asked in our team and [~mlabuda] and [~lvalach] report that Fedora 24 has worked for them without a problem. So I think we can add F24 also. So if PM decides that F25 can be added, we can remove the older versions and have F24 and F25. > Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23636 > URL: https://issues.jboss.org/browse/JBIDE-23636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Labels: releasework > Fix For: 4.4.3.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Ubuntu: > We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases > Fedora: > We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others. > Here's the support matrix document: > https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23490) Server adapter: provide ability to link pods when no service is available

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23490?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23490: ----------------------------------------- [~adietish] Your statement seems correct but I'm not an expert of OpenShift images. [~jeffmaury] seems the best person to answer. > Server adapter: provide ability to link pods when no service is available > ------------------------------------------------------------------------- > > Key: JBIDE-23490 > URL: https://issues.jboss.org/browse/JBIDE-23490 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Aurélien Pupier > Assignee: Jeff MAURY > Labels: new_and_noteworthy, openshift_v3, server_adapter, server_adapter_wizard > Fix For: 4.4.3.Final > > > When some OpenShift applications are not providing any services. the Eclipse OpenShift Tooling is not able to create an OpenShift server adapters to deploy new version of the application. > The only that we are sure that will be always available are pods so it would be nice to provide some fallback logic that asks you to choose a pod or uses the only one it finds when there is no service provided. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23870) Allow edition of Headers for a Jolokia JMX Connection

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23870?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23870: ----------------------------------------- it is far more user-friendly to allow edition. In my case, i made just a typo in header key, I needed to remove it, take care again to what the header value and search again for my Header value which is a token not easily accessible. I had to close the wizard and open another one. So yes, i really think that it is necessary. > Allow edition of Headers for a Jolokia JMX Connection > ----------------------------------------------------- > > Key: JBIDE-23870 > URL: https://issues.jboss.org/browse/JBIDE-23870 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jmx > Affects Versions: 4.4.2.Final > Reporter: Aurélien Pupier > Fix For: 4.5.0.AM1 > > Attachments: image-2017-02-06-14-07-59-965.png > > > currently headers in Edit JMX Connection are not editable. > !image-2017-02-06-14-07-59-965.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3

by Supriya Bharadwaj (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ] Supriya Bharadwaj commented on JBIDE-23636: ------------------------------------------- Docs team is watching this JIRA for updates and will bring this up during the PM call this week. Thanks for all your responses! > Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23636 > URL: https://issues.jboss.org/browse/JBIDE-23636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Labels: releasework > Fix For: 4.4.3.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Ubuntu: > We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases > Fedora: > We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others. > Here's the support matrix document: > https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4270) Problem installing JST Server from RH Central

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4270?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4270. ------------------------------ Resolution: Done I am getting the same results with Devstudio RPM 10.3-0.20170218.1756.el7 and RHSCL-2.4-RHEL-7-20170219.n.0. Closing. > Problem installing JST Server from RH Central > --------------------------------------------- > > Key: JBDS-4270 > URL: https://issues.jboss.org/browse/JBDS-4270 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: build, rpm > Affects Versions: 10.3.0.GA > Reporter: Lukáš Valach > Assignee: Nick Boldt > Fix For: 10.3.0.GA > > Attachments: JST_Server_from_central.png, devstudio_install_jst.png, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JST_Server_from_central_strict.txt > > > The installation of JST Server from Red Hat Central causes problems during the start of eclipse. > There are "Another singleton bundle selected" related to org.eclipse.jst.server. > Log: [^rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.JST_Server_from_central_strict.txt] > Features installed from RH Central: > !JST_Server_from_central.png|thumbnail! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4263) Problems after install from Red Hat Central into rh-eclipse46-devstudio

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4263?page=com.atlassian.jira.plugin.... ] Lukáš Valach updated JBDS-4263: ------------------------------- Fix Version/s: 10.4.0.AM1 (was: 10.3.0.GA) > Problems after install from Red Hat Central into rh-eclipse46-devstudio > ----------------------------------------------------------------------- > > Key: JBDS-4263 > URL: https://issues.jboss.org/browse/JBDS-4263 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: rpm > Affects Versions: 10.3.0.AM2 > Reporter: Nick Boldt > Assignee: Lukáš Valach > Fix For: 10.4.0.AM1 > > Attachments: home_eclipse.txt, opt_rh.txt, rh-eclipse46-devstudio10.3-0.20170206.0203.el7.log.Jboss_Data_Virtualization_Developement_form_IS_repo_strict.txt > > > The installation of software from Red Hat Central causes errors in the log. Some functionality may be broken. We have to test installation of all the stuff from the central and fix the problems. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23788) Hibernate New and Noteworthy for 4.4.3.AM2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23788?page=com.atlassian.jira.plugi... ] Koen Aers closed JBIDE-23788. ----------------------------- Resolution: Done > Hibernate New and Noteworthy for 4.4.3.AM2 > --------------------------------------------------- > > Key: JBIDE-23788 > URL: https://issues.jboss.org/browse/JBIDE-23788 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.4.3.AM2 > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-23786 #comment Create N&N for Hibernate 4.4.3.AM2 #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 Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23788) Hibernate New and Noteworthy for 4.4.3.AM2

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23788?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-23788: ------------------------------ Fix Version/s: 4.4.3.AM2 > Hibernate New and Noteworthy for 4.4.3.AM2 > --------------------------------------------------- > > Key: JBIDE-23788 > URL: https://issues.jboss.org/browse/JBIDE-23788 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: hibernate > Reporter: Jeff MAURY > Assignee: Koen Aers > Priority: Critical > Fix For: 4.4.3.AM2 > > > Koen Aers, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Hibernate 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 Hibernate, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Hibernate 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-23786 #comment Create N&N for Hibernate 4.4.3.AM2 #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 Hibernate for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23623: ------------------------------- Fix Version/s: 4.4.4.AM2 (was: 4.4.4.AM1) > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23623) problems running getProjectRootPomParents and createTaskJIRAs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23623?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23623: ------------------------------------ Cannot proceed without attached console log, so slip to 4.4.4.AM2. > problems running getProjectRootPomParents and createTaskJIRAs > ------------------------------------------------------------- > > Key: JBIDE-23623 > URL: https://issues.jboss.org/browse/JBIDE-23623 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM2 > > Attachments: jira.txt, prepare-am1.txt, run.log > > > When Jeff ran the latest emailed instructions [0] for the 4.4.3.AM1 initialization [1], this happened: > {quote} > Remarks: > the right command is git checkout jbosstools-4.4.x and not co jbosstools-4.4.x > When I run the getProjectRootPomParents.sh script, the JIRAs are not created as createTaskJIRAs.py emits an error message (see run.log). What I do is to get the output using tee, filter the output (keeping only python commands) and then run this script (see jira.txt). Don't know why it does not fail this time. > Would be safe to run `pwd`/util/getProjectRootPomParents.sh instead of ./util/getProjectRootPomParents.sh > Jeff{quote} > [0] https://issues.jboss.org/secure/attachment/12413688/prepare-am1.txt > [1] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017