March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21935) "Reuse" flow in clone wizard is ambiguous

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21935?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-21935: -------------------------------- Summary: "Reuse" flow in clone wizard is ambiguous (was: resue flow in clone wizard is ambigious) > "Reuse" flow in clone wizard is ambiguous > ----------------------------------------- > > Key: JBIDE-21935 > URL: https://issues.jboss.org/browse/JBIDE-21935 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Max Rydahl Andersen > Labels: application_wizard, openshift_v3 > > continuation of JBIDE-14828: > with the intended behavior explained then lets make that visible to the user: > a) don't hide/show controls in a wizard, enable/disable them. > b) The "Reuse" is ambiguous, i.e. I read it as the clone will happen into this folder, not that it will do exactly the opposite of what the wizard says (not clone). I suggest something like "Do not clone - reuse existing folder". > c) if not already there, add a check that what is inside the folder is actually a clone of what we are trying to clone. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3676) BrowserSim cannot start on openjdk (windows)

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3676?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-3676: ----------------------------------- error message fix was pushed to 4.3.x & master > BrowserSim cannot start on openjdk (windows) > -------------------------------------------- > > Key: JBDS-3676 > URL: https://issues.jboss.org/browse/JBDS-3676 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: browsersim > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Ilya Buziuk > Labels: havoc, openjdk > Fix For: 9.1.0.GA > > > Running JBDS on Azul OpenJDK 8, Windows 10. > Starting BrowserSim fails with the following error: > {noformat} > BrowserSim has failed to start with the following error: > "To use BrowserSim please install Safari or run BrowserSim with Oracle Java 7u7 and higher." > Also see BrowserSim FAQ. > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21940) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21940?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21940: ---------------------------------- Fix Version/s: (was: 4.3.1.CR1) > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21940 > URL: https://issues.jboss.org/browse/JBIDE-21940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21940) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21940?page=com.atlassian.jira.plugi... ] Marián Labuda resolved JBIDE-21940. ----------------------------------- Resolution: Done > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21940 > URL: https://issues.jboss.org/browse/JBIDE-21940 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21844) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21844?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21844. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B242. > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21844 > URL: https://issues.jboss.org/browse/JBIDE-21844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21940) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-21940: ------------------------------------- Summary: Deploying specific docker images doesn't always result in a deployment on openshift Key: JBIDE-21940 URL: https://issues.jboss.org/browse/JBIDE-21940 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.3.1.CR1 Reporter: Fred Bricon Assignee: Jeff Cantrill Priority: Critical Fix For: 4.3.1.CR1, 4.4.0.Alpha1 If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21844) Deploying specific docker images doesn't always result in a deployment on openshift

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21844?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21844: ---------------------------------- Fix Version/s: (was: 4.4.0.Alpha1) > Deploying specific docker images doesn't always result in a deployment on openshift > ----------------------------------------------------------------------------------- > > Key: JBIDE-21844 > URL: https://issues.jboss.org/browse/JBIDE-21844 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.3.1.CR1 > > > If I deploy sonatype/nexus to the cdk (OS 3.1.1) or engint (3.1), a deployment is triggered right away. > If I deploy saturnism/spring-boot-helloworld-ui, no deployment is triggered automatically. I need to do it manually -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3656: -------------------------------------- Thanks [~hardy.ferentschik]! Created a new PR to fix that problem - https://github.com/redhat-developer-tooling/developer-platform-install/pu... > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-3656: --------------------------------- Git Pull Request: https://github.com/redhat-developer-tooling/developer-platform-install/pu..., https://github.com/redhat-developer-tooling/developer-platform-install/pu... (was: https://github.com/redhat-developer-tooling/developer-platform-install/pu...) > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3702) Installer: VirtualBox and JDK key in requirements.json should not contain version

by Pavol Pitonak (JIRA)

Pavol Pitonak created JBDS-3702: ----------------------------------- Summary: Installer: VirtualBox and JDK key in requirements.json should not contain version Key: JBDS-3702 URL: https://issues.jboss.org/browse/JBDS-3702 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Reporter: Pavol Pitonak File requirements.json contains URLs to various bits that need to be downloaded in built time or in runtime. VirtualBox and JDK key should *not* contain version. {code:title=requirements.json} "jdk8.zip": { "bundle": "yes", "url": "http://cdn.azul.com/zulu/bin/zulu8.13.0.5-jdk8.0.72-win_x64.zip" }, "vagrant.msi": { "bundle": "no", "url": "https://releases.hashicorp.com/vagrant/1.7.4/vagrant_1.7.4.msi" }, "VirtualBox-5.0.8.exe": { "bundle": "no", "version": "5.0.8", "revision": "103449", "url": "http://download.virtualbox.org/virtualbox/5.0.8/VirtualBox-5.0.8-103449-W..." } {code} -- 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