June 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17453: ------------------------------------- Pushed this to a topic branch on my repo: https://github.com/robstryker/jbosstools-base/compare/JBIDE-17453?expand=1 I'll investigate it further tomorrow for respin-b after talking with david. > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17501) EAP runtime download cannot be finished

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17501?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17501: ------------------------------------- I'm not able to replicate this martin. :| > EAP runtime download cannot be finished > --------------------------------------- > > Key: JBIDE-17501 > URL: https://issues.jboss.org/browse/JBIDE-17501 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.2.0.Beta2 > Environment: JBDS 8.0.0.Beta2a B106 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.2.0.Beta2 > > Attachments: runtime-download-no-finish.png > > > I tried download EAP 6.1 using the runtime download feature. > I hit an issue when I go the path through Server -> New server (it works find if I go through Preferences -> JBoss Tools runtime detection). > I chose EAP 6.1 as server type, then defaults (local, file operations), new runtime. There I clicked Download. > I followed through - the runtime was downloaded, the fields pre-filled. > But now the Finish button is grey and I cannot finish the dialog: > !runtime-download-no-finish.png! -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename (and add version string too?)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-3044: ---------------------------------- Just realized there's another impact to renaming - files in the JBDS install folder ought to ALSO get this makeover: Folder: ~/jbdevstudio/ * jbdevstudio-unity * jbdevstudio -> ./studio/jbdevstudio Folder: ~/jbdevstudio/studio * jbdevstudio * jbdevstudio.ini > Align installation default path with installer filename (and add version string too?) > ------------------------------------------------------------------------------------- > > Key: JBDS-3044 > URL: https://issues.jboss.org/browse/JBDS-3044 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 8.0.0.Beta2 > Reporter: Martin Malina > Assignee: Denis Golovin > Priority: Blocker > Labels: discuss > Fix For: 8.0.0.Beta3 > > > Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync. > This question is open for discussion. Nick pointed out some reasons against this suggestion: > {quote} > Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons: > a) Max is AFK, and will want to vet/veto this idea > b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces > c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience > So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters. > Max Rydahl Andersen WDYT? > {quote} -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17453: ------------------------------------- I've already written an email to [~dhladky]. Because the documentation on this jdf rest api is sparse, I can't remember if I ever specifically agreed to a 200 here, or what the logic was. So I'm not prepared to say their return value is wrong. It may have been a miscommunication somehow, or something else entirely (bad behavior in the rest service?) I'll be bringing it up with david tomorrow. > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17453: -------------------------------- Labels: respin-b (was: respin-a) > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-b > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17408) jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17408?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17408: ------------------------------------ if you apply this change in Beta2x branch, the plugin will be rebuilt and upversioned and people using Beta2a will be able to update to Beta2b. if you apply this change in master branch, the plugin will be rebuilt and upversioned and people using Beta3-some-version will be able to update to Beta3-some-newer-version. Can you apply it, or are you waiting for someone else to do so? > jst.jsdt plugin should depend on SPECIFIC version of tern.java, not just 0.2.0 > ------------------------------------------------------------------------------ > > Key: JBIDE-17408 > URL: https://issues.jboss.org/browse/JBIDE-17408 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Victor Rubezhny > Fix For: 4.2.0.Beta3 > > > Max says (paraphrasing): > "The JSDT stuff should be locked down so that it depends on a specific version of tern.java, not just any version. We want it so that users can only install the version of tern.java we include in our TP." > Currently, this is 0.2.0.201405210810. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-17453: ------------------------------------- Rob, can you raise the issue to the jboss.org team? > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Rob Stryker edited comment on JBIDE-17453 at 6/2/14 12:54 PM: -------------------------------------------------------------- So the jdf download manager rest api is not documnented properly. In fact its documentation is very sparse, though the official download manager rest api is properly documented (no /jdf in the url). It seems it is returning status 200 when the credentials are correct but the workflow has not been completed, ie, user did not yet sign t&c. I was expecting a 403 in this case. What makes it more confusing, though, is that some of you guys seem able to get to the t&c page without issue, which means the rest service must somehow be alternating between 200 or 403. My attempts via curl show a status of 200 is always returned if the credentials are correct and user did not sign t&c, regardless of redirect flag. For now, I'm going to allow either a 403 or a 200 to mean the t&c has not yet been signed. I will also push this to master and beta2. was (Author: rob.stryker): So the jdf download manager rest api is not documnented properly. In fact its documentation is very sparse, though the official download manager rest api is properly documented (no /jdf in the url). It seems it is returning status 200 when the credentials are correct but the workflow has not been completed, ie, user did not yet sign t&c. I was expecting a 403 in this case. What makes it more confusing, though, is that some of you guys seem able to get to the t&c page without issue, which means the rest service must somehow be alternating between 200 or 403. My attempts via curl show a status of 200 is always returned if the credentials are correct and user did not sign t&c. For now, I'm going to allow either a 403 or a 200 to mean the t&c has not yet been signed. I will also push this to master and beta2. > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17453) Error while validating credentials in Download Runtime dialog

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17453?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-17453: ------------------------------------- So the jdf download manager rest api is not documnented properly. In fact its documentation is very sparse, though the official download manager rest api is properly documented (no /jdf in the url). It seems it is returning status 200 when the credentials are correct but the workflow has not been completed, ie, user did not yet sign t&c. I was expecting a 403 in this case. What makes it more confusing, though, is that some of you guys seem able to get to the t&c page without issue, which means the rest service must somehow be alternating between 200 or 403. My attempts via curl show a status of 200 is always returned if the credentials are correct and user did not sign t&c. For now, I'm going to allow either a 403 or a 200 to mean the t&c has not yet been signed. I will also push this to master and beta2. > Error while validating credentials in Download Runtime dialog > ------------------------------------------------------------- > > Key: JBIDE-17453 > URL: https://issues.jboss.org/browse/JBIDE-17453 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.2.0.Beta2 > Reporter: Radoslav Rábara > Assignee: Rob Stryker > Priority: Blocker > Labels: respin-a > Fix For: 4.2.0.Beta2 > > Attachments: credentials validation error.jpg > > > After validation of valid credentials, the following error message appears > {code} > "An error occured while validating your credentials. org.eclipse.core.runtime.CoreException - Unknown response code: 200" > {code} > I was able to reproduce this issue only with one of mine jboss.org accounts. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17507) Central's error message when no connectors can be found needs help

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17507?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-17507: -------------------------------- Assignee: Mickael Istria > Central's error message when no connectors can be found needs help > ------------------------------------------------------------------ > > Key: JBIDE-17507 > URL: https://issues.jboss.org/browse/JBIDE-17507 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery > Affects Versions: 4.2.0.Beta2 > Reporter: Nick Boldt > Assignee: Mickael Istria > > Using vmargs in eclipse.ini / jbdevstudio.ini which pointed to URLs that didn't exist, such as: > {code} > -vmargs > -Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/master/BAD-jbosstools-directory.xml > -Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/core/BAD-master/ > -Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/BAD-master/ > {code} > ... I was able to get this error message in JBDS 8 Beta2: > !https://issues.jboss.org/secure/attachment/12382857/12382857_JBDS8beta2-error-message-squished.png! > Problems: > a) copy is squished into a narrow field - should fill the whole screen > b) "Web" is capitalized. > c) Rather than just saying "you may have a Web connection issue" how about linking the user to the proxy preferences page? -- This message was sent by Atlassian JIRA (v6.2.3#6260)

11 years, 10 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 June 2014