October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21005?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21005: ----------------------------------- Fix Version/s: (was: 3.3.x) > Node location should point to the node executable file instead of the parent folder of it > ----------------------------------------------------------------------------------------- > > Key: JBIDE-21005 > URL: https://issues.jboss.org/browse/JBIDE-21005 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, javascript-bower > Affects Versions: 4.3.0.Final > Reporter: Alexey Kazakov > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > Window->Preferences->Java Script tools->Node > It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. > IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? > WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21005) Node location should point to the node executable file instead of the parent folder of it

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-21005: -------------------------------------- Summary: Node location should point to the node executable file instead of the parent folder of it Key: JBIDE-21005 URL: https://issues.jboss.org/browse/JBIDE-21005 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: javascript, javascript-bower Affects Versions: 4.3.0.Final Reporter: Alexey Kazakov Assignee: Ilya Buziuk Fix For: 3.3.x, 4.4.0.Alpha1 Window->Preferences->Java Script tools->Node It's confusing that "Node Location" in that preference page is actually references to the parent folder of the executable node file. I would expect "/usr/bin/nodejs" or "C:/.../node.exe" in that field. IMO it's confusing and actually not very flexible. Why wouldn't let users to select the executable file itself? WDYT? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20977) XML identation size is not editable

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20977?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20977: --------------------------------------- This is a gtk3 bug. See https://bugs.eclipse.org/bugs/show_bug.cgi?id=428246 and https://bugs.eclipse.org/bugs/show_bug.cgi?id=480335. > XML identation size is not editable > ----------------------------------- > > Key: JBIDE-20977 > URL: https://issues.jboss.org/browse/JBIDE-20977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.CR1b, Eclipse 4.4 > I have Fedora 19, Java 1.7_60, Gnome3, it is both case for JBDS 8.x and Eclipse 4.4 > Colleague of mine has RHEL7 with Gnome, tested on JBDS 8.x as well. > Reporter: Stefan Miklosovic > Assignee: Snjezana Peco > Fix For: 4.4.x > > Attachments: xml-preferences.png > > > !xml-preferences.png! > Window -> Preferencies -> XML -> XML Files -> Editor > Ident using spaces is checked. > Identation size field is not editable, there is still "1" in it. Clicking at arrows (or + - buttons) does not work. I can not rise it to 4 spaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21004?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-21004. --------------------------------- Resolution: Done Fixed in master > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-21004 > URL: https://issues.jboss.org/browse/JBIDE-21004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20717) Inconsistent upper casing in New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20717?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20717. --------------------------------- Assignee: Fred Bricon Resolution: Done Fixed in master/4.3.x > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-20717 > URL: https://issues.jboss.org/browse/JBIDE-20717 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.1.Beta1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog

by Fred Bricon (JIRA)

Fred Bricon created JBIDE-21004: ----------------------------------- Summary: Inconsistent upper casing in New Connection dialog Key: JBIDE-21004 URL: https://issues.jboss.org/browse/JBIDE-21004 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.CR1 Reporter: Marián Labuda Assignee: Fred Bricon Priority: Minor Fix For: 4.3.1.Beta1 There are several places, where upper casing should be more consistent. Label for a default server checkbox is "Use default Server". I think better would be "Use default server" Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21004) Inconsistent upper casing in New Connection dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21004?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21004: -------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta1) > Inconsistent upper casing in New Connection dialog > -------------------------------------------------- > > Key: JBIDE-21004 > URL: https://issues.jboss.org/browse/JBIDE-21004 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.4.0.Alpha1 > > > There are several places, where upper casing should be more consistent. > Label for a default server checkbox is "Use default Server". I think better would be "Use default server" > Secure storage checkbox label "Save Token" or "Save Password" followed by description in parenthesis "(could trigger secure storage)" could follow rest of the dialog. E.g. "Save token (could trigger secure storage)." and "Save password (could trigger secure storage)." -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- btw. what I suggest above is what is used in the jenkins templating. Pretty simple IMO to just abstract this away. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20993: --------------------------------------------- I did not answer anything about ant or maven scripting. I gave examples of variable declaration in general - this issue applies to both maven, shell and ant etc. And no, the same issue apply to devstudio.redhat.com. Reasons why having 10.0 on devstudio and neon on download.jboss.org is a Good Thing: #1 It is very clear if some publishing went wrong. If 10.0 shows up on download.jboss.org or neon on devstudio.redhat.com we know something got messed up. #2 You do not need to have the full hostname to know what kind of deployment we are looking at. #3 10.0 is the actual version of the product so it has a much clearer meaning to users than Neon. Yes, you could argue then we should use version numbers on jboss tools community - but then see reason #1 And no matter if we use maven, ant or shell - none of this matters if the abstraction in property names are which release stream are being referenced, as opposed to devstudioVersion or eclipseBase. So in short - no advantages to having the exact same for this base path (I 100% agree the further sub paths which we constantly publish/update are good to have aligned), but at lest 3 advantages to have a different base path. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20993) http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20993?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-20993 at 10/21/15 1:00 PM: -------------------------------------------------------------- /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting /me sighs I have removed these symlinks: http://download.jboss.org/jbosstools/9.0 http://download.jboss.org/jbosstools/10.0 I will further assume you are OK with keeping the mars and neon symlinks on devstudio.redhat.com. was (Author: nickboldt): /me asks direct question, about shell scripting & maven variables to drive deployment /you answer a different one, about ant scripting *sigh* I will remove the symlinks on download.jboss.org and assume you are OK with keeping them on devstudio.redhat.com. > http://download.jboss.org/jbosstools/ and https://devstudio.redhat.com contain symlinks to map relationship between Eclipse & JBDS versions > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20993 > URL: https://issues.jboss.org/browse/JBIDE-20993 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Fix For: 4.3.1.Beta1 > > > while discussing download.jboss.org with [~dgolovin] we found > http://download.jboss.org/jbosstools/9.0/ > http://download.jboss.org/jbosstools/10.0/ > These look to be links to mars and neon. > This is mixing in devstudio versioning with jbosstools which is just really confusing. > No idea what they are for and I haven't seen/noticed any mails or jiras about introducing a new versioning scheme. > I suggest we delete these ASAP since download.jboss.org is already utterly overloaded with different schemes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 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 October 2015