August 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-391) Enable JSDT Outline view in Neon [EBZ#499788]

by Angel Misevski (JIRA)

[ https://issues.jboss.org/browse/ERT-391?page=com.atlassian.jira.plugin.sy... ] Angel Misevski commented on ERT-391: ------------------------------------ [~ibuziuk], I did have that problem once while testing the change, but it went away after relaunching. Currently, the CompilationUnitStructureVisitor is invoked every time the file is saved, so the outline should update then. I'll look into it more and see if I can figure out what might be going wrong. > Enable JSDT Outline view in Neon [EBZ#499788] > --------------------------------------------- > > Key: ERT-391 > URL: https://issues.jboss.org/browse/ERT-391 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Angel Misevski > Labels: 3.8.1, General, bzira > Fix For: Neon.1 (4.6) > > > As reported in [#1], the Outline view showing the AST of a JavaScript source file is not working properly. > Steps to reproduce: > - unzip and start eclipse-javascript-neon-R > - create a javascript project and paste the code at: http://pastebin.com/BqnJBy5C > - observe the outline does not show the .js AST: http://imgur.com/HMUqjBi.png > This issue is urgent as we have one last sprint before shipping Neon.1. > > [#1] http://stackoverflow.com/questions/38955947/enabling-the-jsdt-outline-vie... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3627: ------------------------------------- Thank you for update. I think we can live with current approach, but update download-manager link to recent cdk release. > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3627: ------------------------------------- Ups, sorry for confusion with comment, I just updated my old comment with curl after you requested it. > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.1.0.AM3 > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4007: ------------------------------------- [~akashche] is that possible to support update when installing on machines with previous installation is present? > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: openjdk.log, screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4007: -------------------------------- Attachment: openjdk.log See attached [^openjdk.log] for 91 to 101 update. > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: openjdk.log, screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4007: ------------------------------------- This is a problem with OpenJDK MSI installer, which does not support update in case previous build is installed. For example if you try to override 91st build with 101st build, you get attached message. Installing the same build twice works fine. We have two options here: 1. Switch to the same approach we still have for vagrant and virtual box and do not allow to install new jdk if another one is present; 2. Switch back zip distribution and that would require make it available in from download manager along with MSI. Currntly only MSI version is available from developers.redhat.com (see https://developers.redhat.com/download-manager/rest/available/openjdk8) > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > Attachments: screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4007: -------------------------------- Priority: Blocker (was: Major) > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Blocker > Fix For: 10.1.0.GA > > Attachments: screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4007) Need a new check for existing OpenJDK installed as an msi package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4007?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4007: -------------------------------- Attachment: screenshot-1.png > Need a new check for existing OpenJDK installed as an msi package > ----------------------------------------------------------------- > > Key: JBDS-4007 > URL: https://issues.jboss.org/browse/JBDS-4007 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM3 > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > Attachments: screenshot-1.png > > > Now that OpenJDK is being installed using the msi installer, a new possible issue has arisen: > Basically it's the same problem we had with Vagrant and Virtualbox - one cannot simply try to reinstall msi package into a different folder. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3931: -------------------------------- Story Points: 1 > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3931) Installed OC binary is not used by default if user has another OC already on system path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3931?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3931: -------------------------------- Status: New (was: New) > Installed OC binary is not used by default if user has another OC already on system path > ---------------------------------------------------------------------------------------- > > Key: JBDS-3931 > URL: https://issues.jboss.org/browse/JBDS-3931 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > Fix For: 10.1.0.GA > > > I tried to install everything on a machine where an existing OC binary was already on path. The newly installed devstudio then used it by default instead of the bundled one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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 August 2016