February 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21732: ---------------------------------- Description: Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me !default_route_os3.gliffy! was: Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me !default_route_os3! > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: default_route_os3.gliffy > > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me > !default_route_os3.gliffy! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21732: ---------------------------------- Description: Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: was:Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: default_route_os3.gliffy > > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21732: ---------------------------------- Description: Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me !default_route_os3! was: Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > Attachments: default_route_os3.gliffy > > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me > !default_route_os3! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3602: ------------------------------------------- We never before had the need for eclipse.buildid - not even sure what to set it too....but if necessary we can. I see in https://bugs.eclipse.org/bugs/show_bug.cgi?id=371419 that this should be a product level property and can be set either in product files or via the build as {code}<property name="eclipse.buildId" value="${unqualifiedVersion}.${buildQualifier}"/>{code} [~nickboldt] [~dgolovin] something you know how to fix ? > Error Reporting doesnt work since we do not set eclipse.buildid > --------------------------------------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > Priority: Blocker > Fix For: 9.1.0.CR1 > > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3602: -------------------------------------- Fix Version/s: 9.1.0.CR1 > Error Reporting doesnt work since we do not set eclipse.buildid > --------------------------------------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > Priority: Blocker > Fix For: 9.1.0.CR1 > > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3602: -------------------------------------- Summary: Error Reporting doesnt work since we do not set eclipse.buildid (was: Error Reporting doesnt work in JBDS) > Error Reporting doesnt work since we do not set eclipse.buildid > --------------------------------------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work since we do not set eclipse.buildid

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3602: -------------------------------------- Priority: Blocker (was: Major) > Error Reporting doesnt work since we do not set eclipse.buildid > --------------------------------------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > Priority: Blocker > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21732: ------------------------------------- Summary: Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard Key: JBIDE-21732 URL: https://issues.jboss.org/browse/JBIDE-21732 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Marián Labuda Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21732) Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21732?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21732: ---------------------------------- Labels: openshift_v3 server_adapter (was: ) > Server Adapter: Improve routing selection group in New OpenShift Server adapter wizard > -------------------------------------------------------------------------------------- > > Key: JBIDE-21732 > URL: https://issues.jboss.org/browse/JBIDE-21732 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3, server_adapter > > Currently there is a group called "Default Route" and there is a selection of a routing and checkbox for it. I would suggest following layout, which seems to be more user friendly for me: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3602) Error Reporting doesnt work in JBDS

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-3602?page=com.atlassian.jira.plugin.... ] Rastislav Wagner commented on JBDS-3602: ---------------------------------------- works with non-empty eclipse.buildId here's what I send from JBDS https://redhat.ctrlflow.com/community/#/incidents/JCURUDCIBnsJJrYPoWNjeUa... > Error Reporting doesnt work in JBDS > ----------------------------------- > > Key: JBDS-3602 > URL: https://issues.jboss.org/browse/JBDS-3602 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: aeri > Affects Versions: 9.1.0.CR1 > Environment: JBDS 9.1.0.CR1-v20160222-0232-B335 > JBT Nightly (2016-02-22) > both contains the same version of aeri plugins > Reporter: Rastislav Wagner > > So I tied to evoke error reporting dialog with the following scenario: > 1. import Java EE Web Project from central > 2. right click in Project Explorer -> refactor -> rename > 3. change name, hit OK which will result in errors from org.hibernate stuff > In case of JBDS no error reporting dialog is shown, works in JBT > I also tried org.eclipse stuff: > 1. open Properties view > 2. create JPA Project (File -> New -> Other... JPA Project) > 3. open persistence.xml which will result in NPE from org.eclipse stuff > And again in no error reporting dialog in case of JBDS but works in JBT -- 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 February 2016