[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ]
Denis Golovin reassigned JBDS-3903:
-----------------------------------
Assignee: Denis Golovin
> Platform Installer does not Setup Docker Env-Vars
> -------------------------------------------------
>
> Key: JBDS-3903
> URL: https://issues.jboss.org/browse/JBDS-3903
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.0.0.Alpha1
> Environment: Windows
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
>
> 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
[JBoss JIRA] (JBDS-3904) Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3904?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3904:
--------------------------------------
Weird error. [~nickboldt] any idea why com.jboss.devstudio.core.usage.branding can't find its own class JBDSUsageBranding?
[~ldimaggio] anything in Eclipse log besides this error?
> Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3904
> URL: https://issues.jboss.org/browse/JBDS-3904
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: build
> Affects Versions: 10.0.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160520-1027-B5398
> Build date: 20160520-1027
> Reporter: Len DiMaggio
>
> This error is logged - and reported to the user if reporting is enabled - on every startup after installation.
> The following report will be sent to JBoss Tools:
> ------
> STATUS
> ------
> pluginId org.eclipse.equinox.ds
> pluginVersion 1.4.400.v20160226-2036
> code 0
> severity 4
> message Exception occurred while creating new instance of component Component[
> name = com.jboss.devstudio.core.usage.branding
> activate = activate
> deactivate = deactivate
> modified =
> configuration-policy = optional
> factory = null
> autoenable = true
> immediate = true
> implementation = com.jboss.devstudio.core.usage.branding.JBDSUsageBranding
> state = Unsatisfied
> properties = {service.ranking=1}
> serviceFactory = false
> serviceInterface = [org.jboss.tools.usage.branding.IUsageBranding]
> references = null
> located in bundle = com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398 [22]
> ]
> fingerprint 922db17c79f930f34d712e9c0d836079
> Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
> at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:270)
> at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:331)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
> at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
> at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
> at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
> at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
> at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:482)
> at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:999)
> at org.eclipse.equinox.internal.p2.core.DefaultAgentProvider.createAgent(DefaultAgentProvider.java:43)
> at org.jboss.tools.central.installation.InstallationChecker.<init>(InstallationChecker.java:66)
> at org.jboss.tools.central.installation.InstallationChecker.getInstance(InstallationChecker.java:84)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6.run(GettingStartedHtmlPage.java:327)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> ------
> REPORT
> ------
> anonymousId dcf4d3ca-83df-4601-b255-94c52db993fc
> name
> email
> comment
> eclipseBuildId 10.0.0.Alpha1-v20160520-1027-B5398
> eclipseProduct com.jboss.devstudio.core.product
> javaRuntimeVersion 1.8.0_65-b17
> osgiWs gtk
> osgiOs Linux
> osgiOsVersion 3.10.0.el7
> osgiArch x86_64
> severity UNKNOWN
> -------
> BUNDLES
> -------
> name org.eclipse.core.jobs
> version 3.8.0.v20160319-0610
> name org.eclipse.equinox.ds
> version 1.4.400.v20160226-2036
> name org.eclipse.equinox.p2.core
> version 2.4.100.v20160419-0834
> name org.eclipse.osgi
> version 3.11.0.v20160427-2120
> name org.jboss.tools.central
> version 2.1.0.Alpha1-v20160510-1913-B866
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3904) Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3904:
----------------------------------
Summary: Error logged at startup - Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
Key: JBDS-3904
URL: https://issues.jboss.org/browse/JBDS-3904
Project: Red Hat Developer Studio (DevStudio)
Issue Type: Bug
Components: build
Affects Versions: 10.0.0.Alpha1
Environment: Version: 10.0.0.Alpha1
Build id: Alpha1-v20160520-1027-B5398
Build date: 20160520-1027
Reporter: Len DiMaggio
This error is logged - and reported to the user if reporting is enabled - on every startup after installation.
The following report will be sent to JBoss Tools:
------
STATUS
------
pluginId org.eclipse.equinox.ds
pluginVersion 1.4.400.v20160226-2036
code 0
severity 4
message Exception occurred while creating new instance of component Component[
name = com.jboss.devstudio.core.usage.branding
activate = activate
deactivate = deactivate
modified =
configuration-policy = optional
factory = null
autoenable = true
immediate = true
implementation = com.jboss.devstudio.core.usage.branding.JBDSUsageBranding
state = Unsatisfied
properties = {service.ranking=1}
serviceFactory = false
serviceInterface = [org.jboss.tools.usage.branding.IUsageBranding]
references = null
located in bundle = com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398 [22]
]
fingerprint 922db17c79f930f34d712e9c0d836079
Exception:java.lang.ClassNotFoundException: com.jboss.devstudio.core.usage.branding.JBDSUsageBranding cannot be found by com.jboss.devstudio.core.usage.branding_10.0.0.Alpha1-v20160520-1027-B5398
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:564)
at org.eclipse.equinox.internal.ds.model.ServiceComponent.createInstance(ServiceComponent.java:493)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.createInstance(ServiceComponentProp.java:270)
at org.eclipse.equinox.internal.ds.model.ServiceComponentProp.build(ServiceComponentProp.java:331)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponent(InstanceProcess.java:620)
at org.eclipse.equinox.internal.ds.InstanceProcess.buildComponents(InstanceProcess.java:197)
at org.eclipse.equinox.internal.ds.Resolver.getEligible(Resolver.java:343)
at org.eclipse.equinox.internal.ds.SCRManager.serviceChanged(SCRManager.java:222)
at org.eclipse.osgi.internal.serviceregistry.FilteredServiceListener.serviceChanged(FilteredServiceListener.java:109)
at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:915)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEventPrivileged(ServiceRegistry.java:862)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.publishServiceEvent(ServiceRegistry.java:801)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistrationImpl.register(ServiceRegistrationImpl.java:127)
at org.eclipse.osgi.internal.serviceregistry.ServiceRegistry.registerService(ServiceRegistry.java:225)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:464)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:482)
at org.eclipse.osgi.internal.framework.BundleContextImpl.registerService(BundleContextImpl.java:999)
at org.eclipse.equinox.internal.p2.core.DefaultAgentProvider.createAgent(DefaultAgentProvider.java:43)
at org.jboss.tools.central.installation.InstallationChecker.<init>(InstallationChecker.java:66)
at org.jboss.tools.central.installation.InstallationChecker.getInstance(InstallationChecker.java:84)
at org.jboss.tools.central.editors.GettingStartedHtmlPage$6.run(GettingStartedHtmlPage.java:327)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
------
REPORT
------
anonymousId dcf4d3ca-83df-4601-b255-94c52db993fc
name
email
comment
eclipseBuildId 10.0.0.Alpha1-v20160520-1027-B5398
eclipseProduct com.jboss.devstudio.core.product
javaRuntimeVersion 1.8.0_65-b17
osgiWs gtk
osgiOs Linux
osgiOsVersion 3.10.0.el7
osgiArch x86_64
severity UNKNOWN
-------
BUNDLES
-------
name org.eclipse.core.jobs
version 3.8.0.v20160319-0610
name org.eclipse.equinox.ds
version 1.4.400.v20160226-2036
name org.eclipse.equinox.p2.core
version 2.4.100.v20160419-0834
name org.eclipse.osgi
version 3.11.0.v20160427-2120
name org.jboss.tools.central
version 2.1.0.Alpha1-v20160510-1913-B866
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-22383:
----------------------------------------
[~adietish], please. Master is frozen until Wed!
> Application Wizard: Selected project combo box is empty
> -------------------------------------------------------
>
> Key: JBIDE-22383
> URL: https://issues.jboss.org/browse/JBIDE-22383
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21302) Removing user from credentials framework while not authenticated to secure storage should not work
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21302?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-21302:
-----------------------------------
Fix Version/s: 4.4.x
(was: 4.4.0.Alpha1)
(was: 4.3.1.CR1)
> Removing user from credentials framework while not authenticated to secure storage should not work
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21302
> URL: https://issues.jboss.org/browse/JBIDE-21302
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: JBDS 9.0.0.Beta1-v20151210-1836-B183
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.4.x
>
>
> Removing credentials (which are stored in secure storage) using
> CredentialPreferencePage without being authenticated to secure storage (see steps to reproduce on how to do that) seems to delete the credentials, but after eclipse restart, the credentials are still there. I would prefer message saying something like "Unable to delete credentials stored in secure storage without atuhenticating to secure storage".
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-22383:
------------------------------------------
+1, works for me, thx!
rebased and merged into master.
> Application Wizard: Selected project combo box is empty
> -------------------------------------------------------
>
> Key: JBIDE-22383
> URL: https://issues.jboss.org/browse/JBIDE-22383
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-22383) Application Wizard: Selected project combo box is empty
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22383?page=com.atlassian.jira.plugi... ]
Andre Dietisheim reassigned JBIDE-22383:
----------------------------------------
Assignee: Viacheslav Kabanovich
Resolution: Done
> Application Wizard: Selected project combo box is empty
> -------------------------------------------------------
>
> Key: JBIDE-22383
> URL: https://issues.jboss.org/browse/JBIDE-22383
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: application_wizard, openshift_v3
> Fix For: 4.4.0.Alpha3
>
>
> Having a connection with several projects and a different than the first one project selected in OpenShift Explorer view, opening of a New OpenShift Application wizard via shell menu File - New - OpenShift Application leaves combo box for a project empty. If the first project is preselect in OpenShift Explorer view, its ok. Issues is only with selected project different than the first one.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months