March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21910: ------------------------------------- If we can detect conflicts, then we should warn the user, explain and let him choose to either - do nothing (user will fix the problem manually) - ask if he want to let the tooling to delete conflicting plugins OR delete .forge folder (i.e. move it to a backup) > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3689) ask user for JDK location when old location is gone

by Aleksandar Kostadinov (JIRA)

Aleksandar Kostadinov created JBDS-3689: ------------------------------------------- Summary: ask user for JDK location when old location is gone Key: JBDS-3689 URL: https://issues.jboss.org/browse/JBDS-3689 Project: Developer Studio (JBoss Developer Studio) Issue Type: Enhancement Components: runtime-detection Affects Versions: 9.1.0.Beta2 Environment: Fedora 23 Reporter: Aleksandar Kostadinov Assignee: Max Rydahl Andersen Hello, installed 9.1.0.Beta2 and starting it after some fedora update, yielded an error that JDK is not found. With no help how to fix. Searching over the internet I found https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Developer_Stu... But it makes much more sense to let the user select a different location. Or at least point user at the ini file to be updated. Currently user is left wondering why JBDS fails to start when system has a perfectly working JDK installed on standard location. My first thought was that for some reason JBDS installation broke. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21910: ----------------------------------------- Pavol, Can you paste the stacktrace in the error log and let us know what's in your ~/.forge? Better have a look at the exception before assuming anything else :) > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21910: ---------------------------------------- I'm trying to understand if it's related to the forge eclipse tooling or a pure forge problem. Does the forge tooling (JBDS) include any addons? If I'm a JBDS 9 or 8 user and updated to JBDS 9.1, what should I do to get this problem? > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] George Gastaldi commented on JBIDE-21910: ----------------------------------------- That´s not a rule, but if you have any addons in {{˜/.forge/addons}} that are already in core, yes, that should be done > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3686) Installer is unpredictable - failing in diff actions

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3686?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3686: -------------------------------------- Looks like download problems. It's one of the reason why we want to have the bundled installer. > Installer is unpredictable - failing in diff actions > ---------------------------------------------------- > > Key: JBDS-3686 > URL: https://issues.jboss.org/browse/JBDS-3686 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10, installer built from src > Reporter: Len DiMaggio > Priority: Critical > Labels: havoc > Attachments: Attempt_1.png, Attempt_2.png, Attempt_3.png, install_log_1.txt, install_log_2.txt, install_log_3.txt > > > See attached log files and screenshots - installer faled in different locations on 3 attempts. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3653) User's home folder with spaces cannot be used by vagrant during install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3653?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3653: -------------------------------------- So it looks like we can't allow users to install in a folder with a space in the path? > User's home folder with spaces cannot be used by vagrant during install > ----------------------------------------------------------------------- > > Key: JBDS-3653 > URL: https://issues.jboss.org/browse/JBDS-3653 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.Beta2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > Attachments: install(1).log > > > Vagrant complains about > {quote}Wed, 02 Mar 2016 18:04:21 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant plugin install c:\DeveloperPlatform\cdk\plugins\vagrant-registration-1.0.0.gem" > The directory where plugins are installed (the Vagrant home directory) > has a space in it. On Windows, there is a bug in Ruby when compiling > plugins into directories with spaces. Please move your Vagrant home > directory to a path without spaces and try again > {quote} > When user home directory have spaces in it, because .vagrant.d file path in turn has spaces as well. For instance: > {code}C:\Users\User Name\.vagrant.d{code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21910: ---------------------------------------- Does it mean that if someone updating JBDS 9 which uses the old version to JBDS 9.1 then Forge won't work out of the box and the ~./forge should be removed first? > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21899) Wrong service is preselected when creating a new OS3 server adapter from context menu of a service

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21899?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21899: ----------------------------------- Fix Version/s: 4.3.1.CR1 > Wrong service is preselected when creating a new OS3 server adapter from context menu of a service > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-21899 > URL: https://issues.jboss.org/browse/JBIDE-21899 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > > When I am creating a new OpenShift 3 server adapter from context menu of a service in OpenShift explorer view and I am having several projects and at least 2 same services (names must be equal) in different projects, then in New OS 3 Server Wizard is wrong service. This is happening when I am trying to create a server adapter from context menu of a service which is lower (in order of tree items under an OpenShift 3 connection) then a service with same name. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ] Alexey Kazakov edited comment on JBIDE-21910 at 3/18/16 9:44 PM: ----------------------------------------------------------------- What's wrong with ~/.forge? Why it should be removed? was (Author: akazakov): What's wrong with ~/.forge? We it should be removed? > Cannot start Forge 3.0.1 runtime - Windows > ------------------------------------------ > > Key: JBIDE-21910 > URL: https://issues.jboss.org/browse/JBIDE-21910 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.CR1 > Environment: windows > Reporter: Pavol Srna > Assignee: George Gastaldi > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: forge-err-xIUnMqLO.png > > > An internal error occurred during: "Starting JBoss Forge 3.0.1.Final" > java.lang.reflect.InvocationTargetException -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016