March 2016 - jbosstools-issues - Jboss List Archives

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

by Pavol Pitonak (JIRA)

[ https://issues.jboss.org/browse/JBDS-3702?page=com.atlassian.jira.plugin.... ] Pavol Pitonak updated JBDS-3702: -------------------------------- Labels: havoc (was: ) > 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 > Labels: havoc > > 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

[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ] Ilya Buziuk closed JBDS-3684. ----------------------------- Resolution: Cannot Reproduce Bug > Preview pane in HTML editor fails with 404 error with OpenJDK > ------------------------------------------------------------- > > Key: JBDS-3684 > URL: https://issues.jboss.org/browse/JBDS-3684 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Priority: Critical > Labels: openjdk > Fix For: 9.1.0.CR1 > > Attachments: preview.png > > > The editor opens the file, and its palette is displayed - the preview pane shows a 404 error. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3684) Preview pane in HTML editor fails with 404 error with OpenJDK

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBDS-3684?page=com.atlassian.jira.plugin.... ] Ilya Buziuk commented on JBDS-3684: ----------------------------------- [~ldimaggio] I tested Preview pane against windows 10 Pro (IE 11.162.10586.0) and was not able to reproduce the issue against oracle, zulu and redhat jdk - HTML preview seems to work just fine. Closing the issue as "Cannot Reproduce". Please, feel free to reopen with additional details > Preview pane in HTML editor fails with 404 error with OpenJDK > ------------------------------------------------------------- > > Key: JBDS-3684 > URL: https://issues.jboss.org/browse/JBDS-3684 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: upstream > Affects Versions: 9.1.0.CR1 > Reporter: Len DiMaggio > Assignee: Ilya Buziuk > Priority: Critical > Labels: openjdk > Fix For: 9.1.0.CR1 > > Attachments: preview.png > > > The editor opens the file, and its palette is displayed - the preview pane shows a 404 error. -- 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 Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3656: ----------------------------------------- How do you install the box file? I assume you are running a _vagrant box add <something>`_? There is difference in the expected box name. In openshift-vagrant the box is called _cdk_v2_, whereas the _Vagrantfile_ of the CDK uses _cdkv2_. So you would need to run: {code} vagrant box add <cdk.box> --name cdkv2 {code} > 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] (JBIDE-21582) Server adapter: always publishes on Eclipse startup

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21582?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-21582. --------------------------------- Verified on nightly build of JBT with OpenShift plugin build B242. > Server adapter: always publishes on Eclipse startup > --------------------------------------------------- > > Key: JBIDE-21582 > URL: https://issues.jboss.org/browse/JBIDE-21582 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > Attachments: usage-on-splash.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21902) Connecting to a OS 3 Server adapter on restarted Eclipse throws error

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21902?page=com.atlassian.jira.plugi... ] Marián Labuda updated JBIDE-21902: ---------------------------------- Description: If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it. {code} The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached. com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication. at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139) at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387) at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287) at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73) at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56) at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} was: If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up {code} An internal error occurred during: "Setting connection, deploy project...". com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication. at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158) at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139) at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387) at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:285) at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:274) at org.jboss.tools.openshift.internal.ui.server.OpenShiftServerEditorSection$13.run(OpenShiftServerEditorSection.java:486) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} > Connecting to a OS 3 Server adapter on restarted Eclipse throws error > --------------------------------------------------------------------- > > Key: JBIDE-21902 > URL: https://issues.jboss.org/browse/JBIDE-21902 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Blocker > Labels: openshift_v3 > > If I am having an OpenShift 3 Server Adapter in Servers view and I restart IDE, I have to fill in credentials again to start OS 3 server adapter. After filling valid credentials using local CDK OS 3.2, following error pops up and server is still stopped. Following attempt to start the server adapter finish successfully (it is because connection is already established, but in first attempt although I was prompted to fill in credentials and connection was some time during the process established, it seems the server adapter was not able to comprehend it. > {code} > The OpenShift service for server eap-app at OpenShift 3 (10.3.2.2) could not be reached. > com.openshift.restclient.authorization.UnauthorizedException: Unauthorized to access resource. You can access the server using Basic authentication. > at com.openshift.internal.restclient.DefaultClient.createOpenShiftException(DefaultClient.java:485) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:158) > at com.openshift.internal.restclient.DefaultClient.list(DefaultClient.java:139) > at org.jboss.tools.openshift.core.connection.Connection.getResources(Connection.java:387) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:287) > at org.jboss.tools.openshift.core.server.OpenShiftServerUtils.getService(OpenShiftServerUtils.java:276) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.pollState(OpenShiftLaunchController.java:73) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:56) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:731) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3556) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3492) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:367) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21859) Collect usage on LiveReload

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21859?page=com.atlassian.jira.plugi... ] Jan Richter commented on JBIDE-21859: ------------------------------------- [~xcoulon], could you give me some directions as to how to verify this? > Collect usage on LiveReload > --------------------------- > > Key: JBIDE-21859 > URL: https://issues.jboss.org/browse/JBIDE-21859 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.3.1.Beta2 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Priority: Critical > Fix For: 4.3.1.CR1 > > > Measure number of installations, LiveReload server starts and maybe even number of requests, grouped by day. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3640) Ensure all required license and source files are present in Vagrant distribution

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3640?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3640. ----------------------------- Closing as we now use the original msi installer. > Ensure all required license and source files are present in Vagrant distribution > -------------------------------------------------------------------------------- > > Key: JBDS-3640 > URL: https://issues.jboss.org/browse/JBDS-3640 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Ken Finnigan > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > https://github.com/redhat-developer-tooling/vagrant-installers, the v1.7.4 branch, is used to generate a Vagrant distribution that is then stored in https://github.com/redhat-developer-tooling/vagrant-distribution, under tag 1.7.4, which is used by the Installer to download Vagrant. > We need to ensure that all licenses and sources are appropriately placed in vagrant-distribution so that the installer can download Vagrant that is correctly licensed. When done it needs to be verified with [~fontana] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3690) Update to CDK Beta5

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3690?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3690. ----------------------------- Verified the change in master, closing. > Update to CDK Beta5 > ------------------- > > Key: JBDS-3690 > URL: https://issues.jboss.org/browse/JBDS-3690 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Labels: havoc > Fix For: 9.1.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3664) Do we still need/want custom build of vagrant ?

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3664?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3664. ----------------------------- Verifying the usage of the original vagrant installer and closing. > Do we still need/want custom build of vagrant ? > ----------------------------------------------- > > Key: JBDS-3664 > URL: https://issues.jboss.org/browse/JBDS-3664 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Components: installer > Reporter: Max Rydahl Andersen > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > we seem to install use our custom vagrant build. > Is that still relevant ? > With that we need to test much more since our build could be different. -- 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