June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22587) install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22587?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22587: ------------------------------------ This was caused by not having bootstrapped the earlyaccess.properties files for the 4.4.x/10.0.x branch: http://download.jboss.org/jbosstools/neon/snapshots/updates/earlyaccess.p... https://devstudio.jboss.com/10.0/snapshots/updates/earlyaccess.properties... Once created, all is well. > install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url > ----------------------------------------------------------------------------------- > > Key: JBIDE-22587 > URL: https://issues.jboss.org/browse/JBIDE-22587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Final > > > {code} > 10:05:00 [2016-06-10T10-5-0] Status ERROR: org.eclipse.mylyn.discovery.core code=0 org.jboss.tools.central.discovery_4.4.0.Final_v20160610_0958_B5.jar_2268305561361558535.jar: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}" org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}", Exception: > 10:05:00 org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}"{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22587) install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22587?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-22587 at 6/13/16 12:22 PM: -------------------------------------------------------------- This was caused by not having bootstrapped the earlyaccess.properties files for the 4.4.x/10.0.x branch: http://download.jboss.org/jbosstools/neon/snapshots/updates/earlyaccess.p... https://devstudio.jboss.com/10.0/snapshots/updates/earlyaccess.properties... Once created, all is well. Could we have a more helpful error message here? was (Author: nickboldt): This was caused by not having bootstrapped the earlyaccess.properties files for the 4.4.x/10.0.x branch: http://download.jboss.org/jbosstools/neon/snapshots/updates/earlyaccess.p... https://devstudio.jboss.com/10.0/snapshots/updates/earlyaccess.properties... Once created, all is well. > install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url > ----------------------------------------------------------------------------------- > > Key: JBIDE-22587 > URL: https://issues.jboss.org/browse/JBIDE-22587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Final > > > {code} > 10:05:00 [2016-06-10T10-5-0] Status ERROR: org.eclipse.mylyn.discovery.core code=0 org.jboss.tools.central.discovery_4.4.0.Final_v20160610_0958_B5.jar_2268305561361558535.jar: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}" org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}", Exception: > 10:05:00 org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}"{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22593) New application wizard: preselect v3 connection that I most recently used

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22593?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22593: ------------------------------------------ [~dbocharov] awesome, thx! > New application wizard: preselect v3 connection that I most recently used > ------------------------------------------------------------------------- > > Key: JBIDE-22593 > URL: https://issues.jboss.org/browse/JBIDE-22593 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitry Bocharov > Labels: application_wizard, connection_wizard, openshift_v2, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Original Estimate: 4 hours > Remaining Estimate: 4 hours > > # ASSERT: make sure that you have used a v3 connection (ex. import an application from your OpenShift server to your workspace) > # EXEC: launch openshift wizard via File->New->OpenShift Application > # ASSERT: connection dialog shows up > Result: > Connection dialog shows up with <New Connection> and connection type "OpenShift 2" pre-selected. > Expected result: > Connection dialog has my v3 connection preselected, that I recently used. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22595: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have *ONLY 1 connection* and it *DOESNT have the password stored* # EXEC: in OpenShift Explorer: select the connection (but *DONT unfold* it) # EXEC: in Docker Explorer: select an image and pick "Deploy to OpenShift..." in its context menu Result: You get prompted to provide the password in 2 dialogs !2-password-dialogs.png! was: # ASSERT: make sure that you have *ONLY 1 connection* and it *DOESNT have the password stored* # EXEC: in OpenShift Explorer: select the connection (but *DONT unfold* it) # EXEC: in Docker Explorer: select an image and pick "Deploy to OpenShift" Result: You get prompted to provide the password in 2 dialogs !2-password-dialogs.png! > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22595: ------------------------------------- Attachment: 2-password-dialogs.png > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22595?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22595: ------------------------------------- Steps to Reproduce: # ASSERT: make sure that you have *ONLY 1 connection* and it *DOESNT have the password stored* # EXEC: in OpenShift Explorer: select the connection (but *DONT unfold* it) # EXEC: in Docker Explorer: select an image and pick "Deploy to OpenShift" Result: You get prompted to provide the password in 2 dialogs !2-password-dialogs.png! was: # ASSERT: make sure that you have ONLY 1 connection and it DOESNT have the password stored # EXEC: in OpenShift Explorer: select the connection # EXEC: in Docker Explorer: select an image and pick "Deploy to OpenShift" Result: You get prompted to provide the password in 2 dialogs !2-password-dialogs.png! > Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-22595 > URL: https://issues.jboss.org/browse/JBIDE-22595 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Final > Reporter: Andre Dietisheim > Fix For: 4.4.1.Alpha1 > > Attachments: 2-password-dialogs.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22595) Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-22595: ---------------------------------------- Summary: Deploy Docker image wizard: One gets 2 authentication dialogs if you're using a non-conected connection without store pw Key: JBIDE-22595 URL: https://issues.jboss.org/browse/JBIDE-22595 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.0.Final Reporter: Andre Dietisheim Fix For: 4.4.1.Alpha1 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ] Alexey Kazakov reassigned JBDS-3903: ------------------------------------ Assignee: Xavier Coulon (was: Denis Golovin) > Platform Installer does not Setup Docker Env-Vars > ------------------------------------------------- > > Key: JBDS-3903 > URL: https://issues.jboss.org/browse/JBDS-3903 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: docker > Affects Versions: 10.0.0.Alpha1 > Environment: Windows > Reporter: Thomas Mäder > Assignee: Xavier Coulon > > I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection. > Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection. > As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22586) JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22586?page=com.atlassian.jira.plugi... ] Nick Boldt closed JBIDE-22586. ------------------------------ Resolution: Done This was caused by having the base_4.4.neon job spin against master instead of 4.4.x branch, then compositing those bits into the JBT site. Purging the bad base bits fixed the problem. > JBT agg site build fetches sources from master instead of 4.4.0.x branch, resulting in SHA conflict. > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-22586 > URL: https://issues.jboss.org/browse/JBIDE-22586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, updatesite > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.0.Final > > Attachments: base-wrong-sources-in-src.zip.png, base-wrong-sources-in-src.zip2.png, base-wrong-sources-in-src.zip3.png > > > For some reason the current JBT agg site build is attempting to fetch sources from master branch instead of 4.4.0.x branch, resulting in this SHA conflict. > {code} > [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.25.0-SNAPSHOT:fetch-sources-from-manifests (fetch-sources) on project org.jboss.tools.site.core: Problem occurred checking upstream buildinfo.json files! > [ERROR] /mnt/hudson_workspace/workspace/jbosstools-build-sites.aggregate.site_4.4.neon/sources/aggregate/site/target/buildinfo/buildinfo_jbosstools-base.json > [ERROR] contains a86fe511763b04d7f43059082ad49aa96bed1bc5, but upstream jbosstools-base project's MANIFEST.MF has Eclipse-SourceReferences > [ERROR] commitId 971627a3892e034feee31845f7a01d1cb45cf585. > [ERROR] If you have locally built projects which are aggregated here, > [ERROR] ensure they are built from the latest SHA from HEAD, not a local topic branch. > [ERROR] Or, use -DskipCheckSHAs=true to bypass this check.{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22587) install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22587?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-22587: ------------------------------- Fix Version/s: 4.4.0.Final (was: 4.4.x) > install grinder: Failed to resolve expression: jboss.discovery.earlyaccess.site.url > ----------------------------------------------------------------------------------- > > Key: JBIDE-22587 > URL: https://issues.jboss.org/browse/JBIDE-22587 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: install-tests > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.0.Final > > > {code} > 10:05:00 [2016-06-10T10-5-0] Status ERROR: org.eclipse.mylyn.discovery.core code=0 org.jboss.tools.central.discovery_4.4.0.Final_v20160610_0958_B5.jar_2268305561361558535.jar: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}" org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}", Exception: > 10:05:00 org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Resolving expression in URL '${jboss.discovery.earlyaccess.site.url}' failed with error: "Failed to resolve expression: ${jboss.discovery.earlyaccess.site.url}"{code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/devst... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 2016