April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22042) Cannot install JBT: Missing requirement: Smart Import support for THyM 0.0.1.201509301541

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22042?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22042: ---------------------------------------- [~psrna] any comments? > Cannot install JBT: Missing requirement: Smart Import support for THyM 0.0.1.201509301541 > ------------------------------------------------------------------------------------------ > > Key: JBIDE-22042 > URL: https://issues.jboss.org/browse/JBIDE-22042 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-a > Fix For: 4.3.1.CR1 > > Attachments: Screen Shot 2016-03-31 at 13.26.03.png > > > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Easymport for Aerogear 1.3.1.CR1-v20160203-2301-B70 (org.jboss.tools.aerogear.easymport.feature.feature.group 1.3.1.CR1-v20160203-2301-B70) > Missing requirement: Smart Import support for THyM 0.0.1.201509301541 (org.eclipse.thym.ui.importer 0.0.1.201509301541) requires 'bundle org.eclipse.e4.ui.importer 0.0.0' but it could not be found > Cannot satisfy dependency: > From: JBoss Easymport for Aerogear 1.3.1.CR1-v20160203-2301-B70 (org.jboss.tools.aerogear.easymport.feature.feature.group 1.3.1.CR1-v20160203-2301-B70) > To: org.eclipse.thym.ui.importer [0.0.1.201509301541] > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21855) Remove/escape the (*) when creating a JIRA Issue from AERI

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21855?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21855: ----------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.1.CR1) > Remove/escape the (*) when creating a JIRA Issue from AERI > ---------------------------------------------------------- > > Key: JBIDE-21855 > URL: https://issues.jboss.org/browse/JBIDE-21855 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aeri > Reporter: Aurélien Pupier > Assignee: Marcel Bruch > Priority: Minor > Fix For: 4.3.1.Final > > > the \(*) need to be escaped otherwise a star is displayed: (*) > BTW: I'm nto sure about the meaning of this \(*) at the end of the line: "The following plug-ins were present on the execution stack" -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3718) Detected/selected JDK always reported as invalid

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3718?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3718: --------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > Detected/selected JDK always reported as invalid > ------------------------------------------------ > > Key: JBDS-3718 > URL: https://issues.jboss.org/browse/JBDS-3718 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.GA > > > The installer correctly detects a JDK but still reports it as invalid. Same goes for selecting an installation of JDK - all checks pass but still the message says the installation is invalid. > It does not seem to be a problem with the detection logic - it returns correct values for me. My guess would be that something is incorrectly propagated to the UI, but I haven't been able to find the source yet. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3741) Developer Studio should install under developer-studio instead of DeveloperStudio

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3741?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3741: --------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > Developer Studio should install under developer-studio instead of DeveloperStudio > --------------------------------------------------------------------------------- > > Key: JBDS-3741 > URL: https://issues.jboss.org/browse/JBDS-3741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Trivial > Labels: havoc > Fix For: 9.1.0.GA > > Attachments: directories.png > > > Currently Developer studio is installed under the folder {{DeveloperStudio}} within the installation directory. All other programs use lower case directory names for their install directory (eg vagrant, cygwun, jdk8, etc). For consistency it should be developerstudio or developer-studio. See screenshot. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3749) With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3749?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3749: --------------------------------- Fix Version/s: 9.1.0.GA (was: 9.1.0.CR1) > With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3749 > URL: https://issues.jboss.org/browse/JBDS-3749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.GA > > Attachments: vb-not-detected-can-not-proceed.png, win10-details.png > > > Downloaded Setup-bundled-0.0.2-20160331-23.exe > Logged in using my RHD credentials > On the Confirmation step of the installer, I see an unchecked box for ORACLE VIRTUALBOX v5 and an unchecked box for "I want to use the existing VirtualBox". > I can't check either of them (when I cursor over them I see a red NOT circle) so as a result the "Download & Install" button is greyed out - it too has a red NOT circle when I cursor over it. > I have VB installed here: > C:\Program Files\Oracle\VirtualBox\VirtualBox.exe > Version 5.0.16 r105871 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22058: --------------------------------------------- what advantage does this have ? if we kill the vm won't it stay dead and we will have to restart the full container anyway ? > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22058: ----------------------------------------------- User can do it by checking the option anyway. [~mlabuda], does that option provide the better user experience? > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich edited comment on JBIDE-22058 at 4/1/16 1:51 PM: ----------------------------------------------------------------------- User can do it by checking the option anyway. [~mlabuda], does that option provide a better user experience? was (Author: scabanovich): User can do it by checking the option anyway. [~mlabuda], does that option provide the better user experience? > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-22058: ------------------------------------- Wait, does it mean we can kill the remote VM? It doesn't sound like a good idea > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22058) Allow termination of remote VM in debug configuration for OpenShift app should be checked by default

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22058?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22058: ----------------------------------------------- [~fbricon], please take a look at the pull request. > Allow termination of remote VM in debug configuration for OpenShift app should be checked by default > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22058 > URL: https://issues.jboss.org/browse/JBIDE-22058 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Labels: openshift_v3 > > The checkbox "Allow termination of remove VM" in debug configuration, which is automatically created and port of forwarder debugging port from pod is set there should be by default enabled to allow user just simply click debug workbench tool item to debug OpenShift application. -- 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 April 2016