January 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21376) Different application proposals on Eclipse tooling vs Web Console

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21376?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21376 at 1/4/16 12:29 PM: ------------------------------------------------------------------- It turns out that this is actually a missing feature. In the web console you can build from template or from builder image (notice the title in the web console "Select Image or Template") with git source. In Eclipse we're missing this. was (Author: adietish): It turns out that this is actually a missing feature. In the web console you can build from template or from builder image (notice the title in the web console "Select Image or Template") with git source. In Eclipse we're missing this yet. > Different application proposals on Eclipse tooling vs Web Console > ----------------------------------------------------------------- > > Key: JBIDE-21376 > URL: https://issues.jboss.org/browse/JBIDE-21376 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Xavier Coulon > Attachments: Screenshot 2015-12-21 16.44.02.png, Screenshot 2015-12-21 16.44.24.png, Screenshot 2015-12-21 18.06.40.png > > > Running OpenShift using our openshift-vagrant box, I can see different proposals between the web console and the Eclipse tooling when adding an application in a project. For example, {{jboss-eap64-openshift:1.1}} is not proposed in the Eclipse tooling. > See attached screenshots. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21165: ---------------------------------------- Added "new_and_noteworthy" to highlight that the preference page for Bower is gone. > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21165: ----------------------------------- Labels: new_and_noteworthy (was: ) > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21165: ----------------------------------- Component/s: javascript > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: javascript, nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21165: ---------------------------------------- For the record. It was merged into upstream JSDT master - https://bugs.eclipse.org/bugs/show_bug.cgi?id=484418 > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21165: ----------------------------------- Component/s: upstream > Need to improve js tools (npm / bower) launch > ---------------------------------------------- > > Key: JBIDE-21165 > URL: https://issues.jboss.org/browse/JBIDE-21165 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: nodejs, upstream > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.4.0.Alpha1 > > > For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available: > {quote} > env: node: No such file or directory > {quote} > In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process. > More details can be found here: > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core... > Basically, this approach kills two birds with one stone: > 1. No mac os Path issue > 2. No need to have preferences for node / npm / bower > Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands > The plan is: > - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future) > - remove irrelevant code with preferences, detectors etc -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21171) Need to remove bower / npm from jboss.tools.jsdt

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21171?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21171: ----------------------------------- Component/s: javascript > Need to remove bower / npm from jboss.tools.jsdt > ------------------------------------------------ > > Key: JBIDE-21171 > URL: https://issues.jboss.org/browse/JBIDE-21171 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, javascript, nodejs > Affects Versions: 4.3.0.Final > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha1 > > > Assuming that bower / npm were moved to eclipse jsdt - https://git.eclipse.org/r/#/c/61336/ > Need to perform a cleanup in jboss.tools.jst.jsdt repo and remove related plugins / tests / features > Bower is in eclipse upstream and we probably will need reflect it in new & noteworthy -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20331) install grinder fails if blocked by Firefox

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20331?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-20331: ------------------------------------ * build 3920 on dev85 failed w/ FF window. Passes: dev88, dev57, dev106 > install grinder fails if blocked by Firefox > ------------------------------------------- > > Key: JBIDE-20331 > URL: https://issues.jboss.org/browse/JBIDE-20331 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Beta2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.x, 4.4.0.Alpha1 > > Attachments: build-history.png, build-history2.png, ff-profile-manager.png, install-grinder-bad-firefox.jpeg, install-grinder-fail.txt, install-grinder-firefox-problem-testInstall(org.jboss.tools.tests.installation.InstallTest).jpeg, new-firefox-block-UI_dev112.png, new-firefox-block-UI_dev59.png, virt1-ftl.png, virt2-ftl.png > > > {code:title=http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-install-grinder.install-tests.matrix_master/PROJECT=jbosstools,eclipseBundleVersion=mars.R,jdk=jdk1.8,label_exp=%28RHEL6||RHEL7||beaker||jboss-prod%29&&%28x86||x86_64%29/3157/consoleFull} > 08:02:18 java.lang.RuntimeException: Unable to aquire PluginConverter service during generation for: /mnt/hudson_workspace/workspace/jbosstools-install-grinder.install-tests.matrix_master/d6768101/eclipse/plugins/org.eclipse.oomph.base_1.1.0.v20150609-0914.jar{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21395) Application wizard: Read-only labels should have a visual hint they're read-only

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21395?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21395: ------------------------------------------ this was merged to master with [79d0b1733ba5a5b8fb3f1a3644973a75894ae13e|https://github.com/adietish/jbos...] > Application wizard: Read-only labels should have a visual hint they're read-only > -------------------------------------------------------------------------------- > > Key: JBIDE-21395 > URL: https://issues.jboss.org/browse/JBIDE-21395 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21395) Application wizard: Read-only labels should have a visual hint they're read-only

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21395?page=com.atlassian.jira.plugi... ] Andre Dietisheim resolved JBIDE-21395. -------------------------------------- Resolution: Done > Application wizard: Read-only labels should have a visual hint they're read-only > -------------------------------------------------------------------------------- > > Key: JBIDE-21395 > URL: https://issues.jboss.org/browse/JBIDE-21395 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Environment: Nightly JBT. OpenShift tooling build Version: 3.1.0.Beta1-v20151104-0336-B66 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Minor > Labels: application_wizard, openshift_v3 > Fix For: 4.3.1.Beta2 > > > Labels in a New OpenShift Application wizard on the page containing label managing are not treated equally. When application is build on a template with more predefined labels, the first one listed in the table with labels is read-only, but the second one (maybe also further labels) are editable and removable. We should treat all labels equally. Either take them as read only from templates or allow user to modify them. As an testing example was used template located at https://github.com/jboss-openshift/application-templates/blob/master/eap/... -- 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 January 2016