June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19953) App import menu items shows odd text

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19953: ------------------------------------- Summary: App import menu items shows odd text Key: JBIDE-19953 URL: https://issues.jboss.org/browse/JBIDE-19953 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Priority: Trivial Attachments: screenshot-1.png Right click on a project and note the import text -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19953) App import menu items shows odd text

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19953?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19953: ---------------------------------- Attachment: screenshot-1.png > App import menu items shows odd text > ------------------------------------ > > Key: JBIDE-19953 > URL: https://issues.jboss.org/browse/JBIDE-19953 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Trivial > Attachments: screenshot-1.png > > > Right click on a project and note the import text -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3450: ---------------------------------- Seems reasonable but bear in mind that `java -version` has to return a JDK 8, not a JRE 8, and not a JRE/JDK 7. Might want to refactor getDefaultJava7Location as getDefaultJavaHome too. would it make sense to change this? {code} diff --git a/installer/src/panels/com/jboss/devstudio/core/installer/JREPathPanel.java b/installer/src/panels/com/jboss/devstudio/core/installer/JREPathPanel.java index 6471774..ec6aefc 100644 --- a/installer/src/panels/com/jboss/devstudio/core/installer/JREPathPanel.java +++ b/installer/src/panels/com/jboss/devstudio/core/installer/JREPathPanel.java @@ -230,7 +230,7 @@ public class JREPathPanel extends PathInputPanel implements IChangeListener { public boolean isValidated() { if(rb1.isSelected()) { - idata.setVariable(getVariableName(), new File(idata.getVariable(VARN_JAVA_HOME)).getPath()); + idata.setVariable(getVariableName(), null); // new File(idata.getVariable(VARN_JAVA_HOME)).getPath()); } else { idata.setVariable(getVariableName(), pathSelectionPanel.getPath()); } {code} Was going to try to get that built & tested but ran out of time before code freeze. > installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3450 > URL: https://issues.jboss.org/browse/JBDS-3450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: jbds-installer_step4-jvm-selection.png > > > {quote} > (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min > (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS. > (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK) > (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine > (2015-06-02 16:39:02) joshuaw: was found after searching the following locations: > (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java > (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java? > (2015-06-02 16:39:40) joshuaw: let me check > 16:40 > (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it > (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :( > (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist? > (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file > (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update? > (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist > (2015-06-02 16:42:32) nickboldt: aha > (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8* > (2015-06-02 16:42:48) nickboldt: pwd > (2015-06-02 16:42:52) nickboldt: put that in your ini file > (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file > (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk > (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39 > (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39 > (2015-06-02 16:46:33) joshuaw: stupid minor minor version update > (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ? > (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file > (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion > (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini > (2015-06-02 17:55:27) nickboldt: -vm > (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > (2015-06-02 17:55:36) maxandersen: thats bad > (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :( > (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ? > {quote} > It's possible the installer is using the CURRENT value of alternatives path for JDK... > {code} > $➔ alternatives --display java > java - status is manual. > link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071 > {code} > So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) Template label decorators don't go away

by Jeff Cantrill (JIRA)

Jeff Cantrill created JBIDE-19952: ------------------------------------- Summary: Template label decorators don't go away Key: JBIDE-19952 URL: https://issues.jboss.org/browse/JBIDE-19952 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.0.Beta1 Reporter: Jeff Cantrill Priority: Minor Attachments: Resource Label dialog.png While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19952) Template label decorators don't go away

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19952?page=com.atlassian.jira.plugi... ] Jeff Cantrill updated JBIDE-19952: ---------------------------------- Attachment: Resource Label dialog.png > Template label decorators don't go away > --------------------------------------- > > Key: JBIDE-19952 > URL: https://issues.jboss.org/browse/JBIDE-19952 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Jeff Cantrill > Priority: Minor > Attachments: Resource Label dialog.png > > > While adding a new label when creating a template, the validation decorator persists and sometime the validation message even for valid labels. See attachment. > Also, noticed focusing away from dialog and back makes them go away. Repainting issue? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19858) jst/jsf New and Noteworthy for 4.3.0.Beta1

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19858?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-19858: -------------------------------------- Assignee: Victor Rubezhny (was: Alexey Kazakov) There is nothing N&N in JST besides some possible important changes in upstream JSDT and/or Tern.java/AngularJS. For example maybe we will update Tern.java/AngularJS to v.0.10: JBIDE-19631 Assigning to [~vrubezhny] to take care of JSDT and Tern.java N&N if any. > jst/jsf New and Noteworthy for 4.3.0.Beta1 > ------------------------------------------ > > Key: JBIDE-19858 > URL: https://issues.jboss.org/browse/JBIDE-19858 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Max Rydahl Andersen > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.3.0.Beta1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3450) installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3450?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3450: ------------------------------------- Possible approach is to run "java -version" and if it fails disable "Default Java VM" add warning at the left of radio "(not found)" or "(not detected)" and fall back to select Specific VM with path initialized from system property "java.home" of current VM. > installer uses a specific JDK as default when installing JBDS; when user updates to newer rpm, jbdevstudio.ini points to non-existent path > ------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-3450 > URL: https://issues.jboss.org/browse/JBDS-3450 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.0.0.Beta1 > Reporter: Nick Boldt > Assignee: Denis Golovin > Fix For: 9.0.0.Beta2 > > Attachments: jbds-installer_step4-jvm-selection.png > > > {quote} > (2015-06-02 16:37:24) joshuaw: maxandersen: I just ran into an issue with JBDS if you have a min > (2015-06-02 16:38:36) joshuaw: I'm running Fedora 22 and it wanted to update, so I let it. I think I had JBDS running when I restarted. When I restarted I couldn't start JBDS. > (2015-06-02 16:39:02) joshuaw: I got the following error: A Java Runtime Environment (JRE) or Java Development Kit (JDK) > (2015-06-02 16:39:02) joshuaw: must be available in order to run Jbdevstudio. No Java virtual machine > (2015-06-02 16:39:02) joshuaw: was found after searching the following locations: > (2015-06-02 16:39:02) joshuaw: /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java > (2015-06-02 16:39:31) nickboldt: does your ~/jbdevstudio/*.ini file point to a SPECIFIC path for java? > (2015-06-02 16:39:40) joshuaw: let me check > 16:40 > (2015-06-02 16:40:10) nickboldt: if alternatives replaced the old JDK w/ newer one the problem is prolly that you're looking in a SPECIFIC place for JVM and Eclipse/JBDS can't find it > (2015-06-02 16:41:37) joshuaw: though the OS update may have moved something :( > (2015-06-02 16:42:10) nickboldt: does /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java exist? > (2015-06-02 16:42:15) joshuaw: nickboldt: yeah, that location is in the .ini file > (2015-06-02 16:42:28) nickboldt: and it actually exists on your disk after the update? > (2015-06-02 16:42:29) joshuaw: nickboldt: that location does not exist > (2015-06-02 16:42:32) nickboldt: aha > (2015-06-02 16:42:45) nickboldt: cd /usr/lib/jvm/java-1.8.0-openjdk-1.8* > (2015-06-02 16:42:48) nickboldt: pwd > (2015-06-02 16:42:52) nickboldt: put that in your ini file > (2015-06-02 16:45:46) joshuaw: I had /usr/lib/jvm/java-1.8.0-openjdk-1.8.0.45-38.b14.fc22.x86_64/bin/java in the .ini file > (2015-06-02 16:45:56) rbenevides is now known as rbenevides|afk > (2015-06-02 16:46:03) joshuaw: and the system now has 1.8.0.45-39 > (2015-06-02 16:46:19) joshuaw: funny how java -version doesn't list the -39 > (2015-06-02 16:46:33) joshuaw: stupid minor minor version update > (2015-06-02 17:46:43) maxandersen: joshuaw: any chance if you recall when you installed if you chose to use the default or specific version of a idk ? > (2015-06-02 17:47:00) maxandersen: joshuaw: if used default it would be a bug if we added specific javavm to the ini file > (2015-06-02 17:55:19) nickboldt: maxandersen: I never pick a specific one, just use default suggestion > (2015-06-02 17:55:27) nickboldt: and I have $➔ cat studio/jbdevstudio.ini > (2015-06-02 17:55:27) nickboldt: -vm > (2015-06-02 17:55:27) nickboldt: /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > (2015-06-02 17:55:36) maxandersen: thats bad > (2015-06-02 17:55:40) nickboldt: so... maxandersen... BUG. :( > (2015-06-02 17:56:19) maxandersen: nickboldt: can you open bug for that one ? > {quote} > It's possible the installer is using the CURRENT value of alternatives path for JDK... > {code} > $➔ alternatives --display java > java - status is manual. > link currently points to /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java > /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.71-2.5.3.0.fc20.x86_64/jre/bin/java - priority 170071 > {code} > So we need to maybe point to a different path... say, in /usr/lib/jvm/jre/ ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-19631: ---------------------------------------- I'm not sure if we should update tern.java & angular.js eclipse to 0.10 for Beta1 but *if* we do so then we have to mantion it in N&N for JBT 4.3.0.Beta1: JBIDE-19858 > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19631) Switch Tern.java dependency version range to the only version after code freeze

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19631?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-19631: ----------------------------------- Labels: new_and_noteworthy (was: ) > Switch Tern.java dependency version range to the only version after code freeze > ------------------------------------------------------------------------------- > > Key: JBIDE-19631 > URL: https://issues.jboss.org/browse/JBIDE-19631 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.3.0.Beta1 > > > In master tern.java dependencies have open range starting from 0.6.0 after https://github.com/jbosstools/jbosstools-jst/pull/429 was applied. > For every development/stable release the open range should be replaced to specific version. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19900) Installing only V3 feature results is limited capability, need to know to install V2

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19900?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-19900: --------------------------------------- [~sspeiche] Installed only v3 tooling from nightly build on 6/5: JBoss OpenShift v3 Tools 3.0.0.Beta2-v20150605-1038-B828 org.jboss.tools.openshift.feature.feature.group JBoss by Red Hat I have new app, delete, import context menu items. [~adietish] mentioned he moved some items around that may have caused the issue previously. > Installing only V3 feature results is limited capability, need to know to install V2 > ------------------------------------------------------------------------------------ > > Key: JBIDE-19900 > URL: https://issues.jboss.org/browse/JBIDE-19900 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Environment: eclipse.buildId=4.5.0.I20150522-2000 > org.jboss.tools.openshift.client (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.common.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift Common UI" [Active] > org.jboss.tools.openshift.core (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > org.jboss.tools.openshift.egit.core (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit Core" [Starting] > org.jboss.tools.openshift.egit.ui (3.0.0.Beta1-v20150528-1036-B807) "OpenShift EGit UI" [Starting] > org.jboss.tools.openshift.ui (3.0.0.Beta1-v20150528-1036-B807) "Bundle-Name" [Active] > Reporter: Steve Speicher > Assignee: Jeff Cantrill > Fix For: 4.3.0.Beta1 > > Attachments: Screen Shot 2015-05-29 at 5.11.03 PM.png > > > If a user is interested in only V3, they are tempted to just install the V3 feature. The issue is that a number of things don't work, namely the "Create"/"New" paths. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

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