March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20446) Hibernate 5.0 support

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20446?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20446: ----------------------------------- Labels: new_and_noteworthy (was: ) > Hibernate 5.0 support > --------------------- > > Key: JBIDE-20446 > URL: https://issues.jboss.org/browse/JBIDE-20446 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: hibernate > Affects Versions: 4.3.0.Beta2 > Environment: JBDS 9.0.0.Beta2 > Reporter: Jiri Peterka > Assignee: Koen Aers > Labels: new_and_noteworthy > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > Hibernate 5.0 is close to be released (CR4 at the time of writing this JIRA). JBoss Tools Hibernate Tools should support this latest version. Would be good to have it in JBDS 9.0.GA at least in form of early access or experimental feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21616) Main tab for CDK launch configuration is not whole by default

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21616?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-21616: --------------------------------------- [~mlabuda] What version of GTK are you using? > Main tab for CDK launch configuration is not whole by default > ------------------------------------------------------------- > > Key: JBIDE-21616 > URL: https://issues.jboss.org/browse/JBIDE-21616 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.3.1.CR1 > Environment: Fedora 22, GTK3 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > Attachments: after.png, before.png > > > In launch configuration of a CDK server adapter there are 2 tabs - Main and Environment. Upon opening of launch configuration for a CDK server adapter, Main tab is preselected but there are only Location widgets available. > !before.png! > After switching to Environment tab and back, Working directory and Arguments widgets become available. > !after.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3622) Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Len DiMaggio commented on JBDS-3622: ------------------------------------ Agreed! Every screen must provide the user with the option of cancelling the install. > Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3622 > URL: https://issues.jboss.org/browse/JBDS-3622 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: installing.png, install_error.png > > > See the attached screenshot - the install has failed - the only option for the user is to close the installer window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3666) Back off and retry if download fails

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3666?page=com.atlassian.jira.plugin.... ] Josephine Qian edited comment on JBDS-3666 at 3/16/16 2:34 PM: --------------------------------------------------------------- [~dgolovin][~jowilson]Please see the updated design: https://goo.gl/photos/RZbZkR8n3DM7d4aK9 Clicking on the Download Again button will initiate the download for the failed components. was (Author: joqian): Please see the updated design: https://goo.gl/photos/RZbZkR8n3DM7d4aK9 Clicking on the Download Again button will initiate the download for the failed components. > Back off and retry if download fails > ------------------------------------ > > Key: JBDS-3666 > URL: https://issues.jboss.org/browse/JBDS-3666 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Blocker > Labels: Havoc > Fix For: 9.1.0.CR1 > > > We should back off and retry downloads when they fail, automatically. We should also off a manual retry button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3666) Back off and retry if download fails

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3666?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3666: -------------------------------------- Please see the updated design: https://goo.gl/photos/RZbZkR8n3DM7d4aK9 Clicking on the Download Again button will initiate the download for the failed components. > Back off and retry if download fails > ------------------------------------ > > Key: JBDS-3666 > URL: https://issues.jboss.org/browse/JBDS-3666 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Story > Components: installer > Reporter: Pete Muir > Assignee: Denis Golovin > Priority: Blocker > Labels: Havoc > Fix For: 9.1.0.CR1 > > > We should back off and retry downloads when they fail, automatically. We should also off a manual retry button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3622) Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3622: -------------------------------------- Regardless of the Close icon at the top right, I think there should be always a Cancel button on every screen, on the left of the blue button > Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3622 > URL: https://issues.jboss.org/browse/JBDS-3622 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: installing.png, install_error.png > > > See the attached screenshot - the install has failed - the only option for the user is to close the installer window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21705) update tools.jboss.org/usage with error reporting tracking details

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21705?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21705: ---------------------------------------- I would wait. > update tools.jboss.org/usage with error reporting tracking details > ------------------------------------------------------------------ > > Key: JBIDE-21705 > URL: https://issues.jboss.org/browse/JBIDE-21705 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, usage > Reporter: Max Rydahl Andersen > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > usage page should not just talk about Google analytics, but aslo about error reporting. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3626) Error message about not signed T&C agreement should give users info how to sign it

by Josephine Qian (JIRA)

[ https://issues.jboss.org/browse/JBDS-3626?page=com.atlassian.jira.plugin.... ] Josephine Qian commented on JBDS-3626: -------------------------------------- After discussing with Denis, we decided to wait for the new page before we design anything for this issue. > Error message about not signed T&C agreement should give users info how to sign it > ---------------------------------------------------------------------------------- > > Key: JBDS-3626 > URL: https://issues.jboss.org/browse/JBDS-3626 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Alexey Kazakov > Assignee: Joshua Wilson > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: You_re_almost_there___Red_Hat_Developers.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21829) Error while opening Eclipse with OpenShift Server Editor opened

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21829?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-21829: --------------------------------------- Please rebase on latest and enable tracing and post the rest client call here. I'm interested in learning which namespace it says it is trying to list services. > Error while opening Eclipse with OpenShift Server Editor opened > --------------------------------------------------------------- > > Key: JBIDE-21829 > URL: https://issues.jboss.org/browse/JBIDE-21829 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Jeff Cantrill > Fix For: 4.3.1.CR1 > > > I get the following error when my runtime Eclipse starts with the Server Editor opened on an OpenShift Server Adapter: > {code} > !ENTRY org.eclipse.core.jobs 4 2 2016-03-08 15:54:58.597 > !MESSAGE An internal error occurred during: "Setting connection, deploy project...". > !STACK 0 > com.openshift.restclient.authorization.ResourceForbiddenException: User "test-admin" cannot list all services in the cluster > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:477) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:152) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:133) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:128) > at org.jboss.tools.openshift.core.connection.Connection.retryList(Connection.java:434) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:377) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:267) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:256) > at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} > This error also happens when the editor is closed at start-up and opened later on. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3566) include AERI in JBDS 9.1

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3566?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-3566 at 3/16/16 2:10 PM: ----------------------------------------------------------- OK, figured out what the problem is on my system. AERI doesn't trigger a dialog IN Eclipse. It triggers an OS-level alert. So... OOTB, nothing happens on my system until I do this: {code} export SWT_GTK3=0 {code} Then the dialog appears exactly as described. Steps to repro: 1. install JBDS, launch from installer 2. Help > Install new > http://download.eclipse.org/technology/epp/logging/milestones > EPP Logging Manual Tests Feature > shut down JBDS 3. export SWT_GTK3=0 4. launch JBDS 5. from the Log Error dropdown in the coolbar, select Trigger JBoss Error [^aeri-popup.png] --- Verified dialog appears with these versions: * jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar * jboss-devstudio-10.0.0.Alpha1-v20160316-1022-B4975-installer-standalone.jar And was able to submit a report here: https://redhat.ctrlflow.com/community/#/incidents/Nr5PUidTzbV6S4QqAp2akuI... was (Author: nickboldt): OK, figured out what the problem is on my system. AERI doesn't trigger a dialog IN Eclipse. It triggers an OS-level alert. So... OOTB, nothing happens on my system until I do this: {code} export SWT_GTK3=0 {code} Then the dialog appears exactly as described. [^aeri-popup.png] Verified dialog appears with these versions: * jboss-devstudio-9.1.0.CR1-v20160311-1249-B402-installer-standalone.jar * jboss-devstudio-10.0.0.Alpha1-v20160316-1022-B4975-installer-standalone.jar And was able to submit a report here: https://redhat.ctrlflow.com/community/#/incidents/Nr5PUidTzbV6S4QqAp2akuI... > include AERI in JBDS 9.1 > ------------------------ > > Key: JBDS-3566 > URL: https://issues.jboss.org/browse/JBDS-3566 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: aeri, build, target-platform > Affects Versions: 9.1.0.Beta1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.CR1 > > Attachments: aeri-in-jbds91.png, aeri-not-firing.png, aeri-popup.png, error-prefs-jbds.png, error-prefs-jbt.png, error-reporting.png > > > Include required bundles for AERI in JBDS. Details TBD. > Maybe need these? > {code} > org.eclipse.epp.logging.aeri.feature_1.0.1.v20150913-0716 > org.eclipse.epp.logging.aeri.ide_1.0.1.v20150913-0657.jar > org.eclipse.epp.logging.aeri.ui_1.0.1.v20150913-0716.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 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 March 2016