[JBoss JIRA] (JBIDE-20004) OpenShift v3 resources names should be camelcasized or splitted by space character
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20004?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-20004:
----------------------------------
Priority: Minor (was: Major)
> OpenShift v3 resources names should be camelcasized or splitted by space character
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-20004
> URL: https://issues.jboss.org/browse/JBIDE-20004
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Priority: Minor
>
> Currently OpenShift v3 resources are as one long name and without camel case practice or spaces or spaces with capitalized first letters. It would be better to have more appropriate format.
> Affected resources:
> * Buildconfigs should be "Build configs" or "BuildConfigs" or "Build Configs"
> * Deploymentsconfigs should be "Deployment configs" or "DeploymentConfigs" or "Deployment Configs"
> * Imagestream should be "Image streams" or "ImageStreams" or "Image Streams"
> * Replicationcontrollers should be "Replication controllers" or "ReplicationControllers" or "Replication Controllers"
> I would suggest to use capitalized separated wording but I leave it up to decision of developer.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19845) Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19845?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-19845.
---------------------------------
Verified in JBDS 9.0.0.Beta1 build id B34.
> Project context menu: Creating a new OpenShift application via Configure always uses first connection from OpenShift Explorer view
> ----------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19845
> URL: https://issues.jboss.org/browse/JBIDE-19845
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta1
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: application_wizard
> Fix For: 4.3.0.Beta1
>
>
> If user wants to create a new OpenShift application via context menu of a project, it is possible to do it via context menu "Configure - New/Import OpenShift application". Previously this selection prompted user to choose desired connection where to create a new application. Nowadays the first existing connection in OpenShift explorer view is selected and it is not possible to change connection.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-17103) No warning/error is shown when detected runtime fails to be added
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17103?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17103.
---------------------------------
Verified in JBDS 9.0.0.Beta1 B34. I was able to get that error if I removed the server after it was found. Also, currently you can get this error for WildFly 10 - it is found, but not added, so this error also shows up. Personally, I would prefer more readable text like "Unable to add runtimes." rather than "Unable to initialize some runtime paths." - that seems a bit cryptic to me. But I guess it's just me ;)
> No warning/error is shown when detected runtime fails to be added
> -----------------------------------------------------------------
>
> Key: JBIDE-17103
> URL: https://issues.jboss.org/browse/JBIDE-17103
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
> Attachments: JBIDE-17103.png
>
>
> When there is a new version of a runtime, e.g. WildFly 8.1, that is not yet supported by the tooling, runtime detection usually detects it alright, but when you then click OK, the runtime+server are not added. And there is no error anywhere at all - we should fix that.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19291) "Unable to execute early startup code ..." exception after starup.
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19291?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-19291.
---------------------------------
I haven't seen this error in JBDS 9.0.0.Beta1 B34 so far, so I'm closing this. [~rhopp], let us know if your experience is different.
> "Unable to execute early startup code ..." exception after starup.
> ------------------------------------------------------------------
>
> Key: JBIDE-19291
> URL: https://issues.jboss.org/browse/JBIDE-19291
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1
> Reporter: Radim Hopp
> Assignee: Rob Stryker
> Fix For: 4.3.0.Beta1
>
>
> After startup in error log there is this error:
> {noformat:title=Unable to execute early startup code for the org.eclipse.ui.IStartup extension contributed by the 'org.jboss.ide.eclipse.as.ui' plug-in.}
> org.eclipse.core.runtime.CoreException: Executable extension definition for "class" not found.
> at org.eclipse.core.internal.registry.ConfigurationElement.throwException(ConfigurationElement.java:62)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:222)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.WorkbenchPlugin$1.run(WorkbenchPlugin.java:293)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:52)
> at org.eclipse.ui.internal.WorkbenchPlugin.createExtension(WorkbenchPlugin.java:288)
> at org.eclipse.ui.internal.EarlyStartupRunnable.getExecutableExtension(EarlyStartupRunnable.java:102)
> at org.eclipse.ui.internal.EarlyStartupRunnable.run(EarlyStartupRunnable.java:54)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.Workbench$56.run(Workbench.java:2801)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20003) Add Refresh context menu item to OpenShift v3 projects
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20003:
-------------------------------------
Summary: Add Refresh context menu item to OpenShift v3 projects
Key: JBIDE-20003
URL: https://issues.jboss.org/browse/JBIDE-20003
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Priority: Minor
There could be Refresh context menu item on project for OpenShift v3 connections. Similar as the one in context menu of OpenShift v3 connections.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months