January 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-571) 528414 – Launcher segfault under Wayland when openFile is used

by Leo Ufimtsev (JIRA)

[ https://issues.jboss.org/browse/ERT-571?page=com.atlassian.jira.plugin.sy... ] Leo Ufimtsev updated ERT-571: ----------------------------- Sprint: devex #142 December 2017, devex #143 January 2018 (was: devex #142 December 2017) > 528414 – Launcher segfault under Wayland when openFile is used > -------------------------------------------------------------- > > Key: ERT-571 > URL: https://issues.jboss.org/browse/ERT-571 > Project: Eclipse Release Train > Issue Type: Task > Reporter: Leo Ufimtsev > Assignee: Leo Ufimtsev > Labels: SWT > Original Estimate: 3 weeks > Remaining Estimate: 3 weeks > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (ERT-573) Stage 1: Implement very simple mechanism with gdbus to open file in any eclipse instance

by Leo Ufimtsev (JIRA)

[ https://issues.jboss.org/browse/ERT-573?page=com.atlassian.jira.plugin.sy... ] Leo Ufimtsev closed ERT-573. ---------------------------- Resolution: Done > Stage 1: Implement very simple mechanism with gdbus to open file in any eclipse instance > ---------------------------------------------------------------------------------------- > > Key: ERT-573 > URL: https://issues.jboss.org/browse/ERT-573 > Project: Eclipse Release Train > Issue Type: Sub-task > Reporter: Leo Ufimtsev > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25548) CDT Meson support (Managed Build)

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25548?page=com.atlassian.jira.plugi... ] Jeff Johnston updated JBIDE-25548: ---------------------------------- Labels: ERT (was: ) > CDT Meson support (Managed Build) > --------------------------------- > > Key: JBIDE-25548 > URL: https://issues.jboss.org/browse/JBIDE-25548 > Project: Tools (JBoss Tools) > Issue Type: Task > Reporter: Jeff Johnston > Assignee: Jeff Johnston > Labels: ERT > > Add Meson build support to the CDT. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25548) CDT Meson support (Managed Build)

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25548?page=com.atlassian.jira.plugi... ] Jeff Johnston updated JBIDE-25548: ---------------------------------- Sprint: devex #143 January 2018 > CDT Meson support (Managed Build) > --------------------------------- > > Key: JBIDE-25548 > URL: https://issues.jboss.org/browse/JBIDE-25548 > Project: Tools (JBoss Tools) > Issue Type: Task > Reporter: Jeff Johnston > Assignee: Jeff Johnston > > Add Meson build support to the CDT. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25548) CDT Meson support (Managed Build)

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25548?page=com.atlassian.jira.plugi... ] Jeff Johnston reassigned JBIDE-25548: ------------------------------------- Assignee: Jeff Johnston > CDT Meson support (Managed Build) > --------------------------------- > > Key: JBIDE-25548 > URL: https://issues.jboss.org/browse/JBIDE-25548 > Project: Tools (JBoss Tools) > Issue Type: Task > Reporter: Jeff Johnston > Assignee: Jeff Johnston > > Add Meson build support to the CDT. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25548) CDT Meson support (Managed Build)

by Jeff Johnston (JIRA)

Jeff Johnston created JBIDE-25548: ------------------------------------- Summary: CDT Meson support (Managed Build) Key: JBIDE-25548 URL: https://issues.jboss.org/browse/JBIDE-25548 Project: Tools (JBoss Tools) Issue Type: Task Reporter: Jeff Johnston Add Meson build support to the CDT. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24961) New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24961?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24961: ------------------------------- Sprint: devex #143 January 2018 (was: devex #142 December 2017) > New Application Wizard: include "Import Project" and "Server adapter creation" into the wizard > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-24961 > URL: https://issues.jboss.org/browse/JBIDE-24961 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

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

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24797: ------------------------------- Sprint: devex #139 October 2017, devex #143 January 2018 (was: devex #139 October 2017, devex #142 December 2017) > 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.x > > > 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.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25547: ------------------------------------- Description: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area !connection-wizard.png! Result: You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more. Expected result: Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there. was: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area !connection-wizard.png! Result: You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences Expected result: Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there. > Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25547 > URL: https://issues.jboss.org/browse/JBIDE-25547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > Attachments: connection-wizard.png > > > # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location > # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid > (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) > # EXEC: launch connection wizard > # EXEC: provide server url and authentication means > # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area > !connection-wizard.png! > Result: > You cannot save your connection unless you override the oc location for this connection. In order to correct the preferences you have to cancel the wizard and go to the preferences. Once you correct the value in preferences, you are not prevented from saving the connection any more. > Expected result: > Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25547) Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25547?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25547: ------------------------------------- Description: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area !connection-wizard.png! Result: You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences Expected result: Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there. was: # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) # EXEC: launch connection wizard # EXEC: provide server url and authentication means # ASSERT: "Finish" is still disabled, an error about oc location is show in the title area !connection-wizard.png! Result: You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences Expected result: Either allow saving the connection even with an invalid oc location or allow to get to the preferences. > Connection wizard: cannot save connection if "oc location" in preferences is invalid unless you override > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-25547 > URL: https://issues.jboss.org/browse/JBIDE-25547 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.AM3 > Reporter: Andre Dietisheim > Fix For: 4.5.x > > Attachments: connection-wizard.png > > > # ASSERT: make sure that you have the location to the oc binary set in OpenShift 3 preferences JBoss Tools > OpenShift 3 > 'oc' executable location > # EXEC: rename the oc (that your preferences point to) so that the preferences value gets invalid > (this happens if you setup a new cdk since you have to kill your .minishift and the path to the oc contains a folder named after the version of it: ex. ~/.minishift/cache/oc/v3.6.173.0.21/oc) > # EXEC: launch connection wizard > # EXEC: provide server url and authentication means > # ASSERT: "Finish" is still disabled, an error about oc location is shown in the title area > !connection-wizard.png! > Result: > You cannot save your connection unless you override the oc location for this connection. I order to correct the preferences I have to cancel the wizard and go to the preferences > Expected result: > Either allow saving the connection even with an invalid oc location in preferences or allow to get to the preferences and correct it there. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 2 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 January 2018