[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-14890:
----------------------------------
Comment: was deleted
(was: Closing because there is not going to be any time to fix openshift related JIRAs with fixVersion set to LATER.)
> Application wizard: Use EGit recursive merge instead of copying git repository
> ------------------------------------------------------------------------------
>
> Key: JBIDE-14890
> URL: https://issues.jboss.org/browse/JBIDE-14890
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.1.0.Beta2, 4.1.1.Final
> Reporter: Andre Dietisheim
> Labels: application_wizard
> Fix For: LATER
>
> Attachments: user-existing-project.png
>
>
> OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing")
> !user-existing-project.png!
> When using the git command line one is told to merge by using the recursive merge startegy:
> {code}
> git merge -s recursive -X ours foo
> {code}
> When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over.
> EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20155) Cannot create a new OpenShift v3 application on staging openshift because api version v1 is not supported for Service
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20155:
-------------------------------------
Summary: Cannot create a new OpenShift v3 application on staging openshift because api version v1 is not supported for Service
Key: JBIDE-20155
URL: https://issues.jboss.org/browse/JBIDE-20155
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Priority: Blocker
When I am trying to create a new OpenShift v3 application on a template on stg.openshift.com I get following error in case of build configs with apiVersion v1 for Service
{code}
java.lang.RuntimeException: com.openshift.restclient.ResourceFactoryException: There was an exception creating the resource from: {"kind" : "Service", "apiVersion" : "v1", "spec" : {"ports" : [{"port" : 8080, "targetPort" : 8080}], "selector" : {"deploymentConfig" : "${APPLICATION_NAME}"}}, "metadata" : {"name" : "${APPLICATION_NAME}-http-service", "labels" : {"application" : "${APPLICATION_NAME}"}, "annotations" : {"description" : "The web server's http port."}}}
at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:65)
at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:54)
at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:85)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:111)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:58)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:487)
at org.eclipse.core.databinding.ValueBinding$3$1.run(ValueBinding.java:206)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:196)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158)
at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147)
at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
at org.eclipse.jface.internal.databinding.viewers.SelectionChangedListener.selectionChanged(SelectionChangedListener.java:36)
at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
at org.eclipse.jface.window.Window.open(Window.java:803)
at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:244)
at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:46)
at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Caused by: com.openshift.restclient.ResourceFactoryException: There was an exception creating the resource from: {"kind" : "Service", "apiVersion" : "v1", "spec" : {"ports" : [{"port" : 8080, "targetPort" : 8080}], "selector" : {"deploymentConfig" : "${APPLICATION_NAME}"}}, "metadata" : {"name" : "${APPLICATION_NAME}-http-service", "labels" : {"application" : "${APPLICATION_NAME}"}, "annotations" : {"description" : "The web server's http port."}}}
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:149)
at com.openshift.internal.restclient.model.template.Template.getItems(Template.java:70)
at org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizardModel.setTemplate(NewApplicationWizardModel.java:80)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:483)
at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59)
... 103 more
Caused by: com.openshift.restclient.ResourceFactoryException: Unable to create v1 resource kind Service from {
"kind" => "Service",
"apiVersion" => "v1",
"spec" => {
"ports" => [{
"port" => 8080,
"targetPort" => 8080
}],
"selector" => {"deploymentConfig" => "${APPLICATION_NAME}"}
},
"metadata" => {
"name" => "${APPLICATION_NAME}-http-service",
"labels" => {"application" => "${APPLICATION_NAME}"},
"annotations" => {"description" => "The web server's http port."}
}
}
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:166)
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:147)
... 110 more
Caused by: java.lang.RuntimeException: Version 'v1' not supported for kind 'Service'
at com.openshift.internal.restclient.model.properties.ResourcePropertiesRegistry.get(ResourcePropertiesRegistry.java:101)
at com.openshift.internal.restclient.ResourceFactory.create(ResourceFactory.java:162)
... 111 more
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19838) Add back button to Software/Upate page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19838?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-19838:
-------------------------------------
[~mickael_istria] do you want to take a look at that one for Beta2, or else I'll punt it since I'll go on PTO this monday.
> Add back button to Software/Upate page
> --------------------------------------
>
> Key: JBIDE-19838
> URL: https://issues.jboss.org/browse/JBIDE-19838
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Beta1
> Environment: JBT 4.3.0.Nightly, central feature version 2.0.0.Beta1-v20150520-1916-B702
> Reporter: Radim Hopp
> Fix For: 4.3.0.Beta2
>
>
> Now in new Central, there is big Add Tools button which switches central to Software/Update page.
> Now, I can imagine some people struggling with switching back to Central form Software/Update page. The tabs on bottom are easy to overlook (when it's ones first encountering with central). It would be good IMHO to have some "back" button on Software/Update page.
> With old central it was OK, because switching to Software/Update page required user to notice those tabs on the bottom. No one can be completely unaware of those.
> What do you think?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20154) Forge console output writes slowly on OSX
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20154?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-20154:
----------------------------------------
Project: Tools (JBoss Tools) (was: Developer Studio (JBoss Developer Studio))
Key: JBIDE-20154 (was: JBDS-3474)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Affects Version/s: (was: 9.0.0.Beta1)
Component/s: forge
(was: forge)
Docs QE Status: (was: NEW)
> Forge console output writes slowly on OSX
> -----------------------------------------
>
> Key: JBIDE-20154
> URL: https://issues.jboss.org/browse/JBIDE-20154
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Environment: OSX 10.10.3
> Java 1.8.0_45_b14
> Reporter: Lincoln Baxter III
> Assignee: Max Rydahl Andersen
>
> The force console writes much more slowly on OSX than it does on Windows and Unix.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-20153) Docker server adapter
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-20153:
-------------------------------------------
Summary: Docker server adapter
Key: JBIDE-20153
URL: https://issues.jboss.org/browse/JBIDE-20153
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: docker, server
Reporter: Max Rydahl Andersen
Priority: Critical
I've been wondering for a time what would be the best way to integrate docker with our server adapters.
I initially first thought it should be an additional profile to the existing local or remote profiles - but I think that option actually ends up being too limiting. To start - the server inside the docker then is assumed to always be a wildfly server; and I think for docker that is too limiting.
Watching Eclipse Che demo at EclipseCon I realized their approach for "Runners" actually fits perfectly.
What they do is that they don't actually have any insight into what servers they are running - they simply just have an associated DockerFile for a "runner" which they build and then run before launching.
Once launched they then know where the server port is, where the possible debug port is, where files are mounted etc.
So this Docker Server Adapter can be made to run *any* kind of application.
WildFly, Tomcat, Python, even plain java apps.
And actually it is not just a DockerFile that is associated with the run but a templated dockerfile. A file where certain variables will be replaced; like:
{code}
VOLUME /deployments
ADD $app$ /deployments
{code}
will add the packaged app (i.e. wonka.war) into the /deployments folder and /deployments is mounted.
And actually the /deployments can then be updated incrementally if wanted to.
Even greater is that if we could support the same syntax and semantics of the templating we can simply reuse the templates defined by Che at https://github.com/codenvy/dockerfiles/
You can see more complete info on what codenvy/che does http://docs.codenvy.com/user/builders-and-runners/#custom-machines
This would cover all the usecases I can currently think of with launching docker from eclipse - but not be tied to any specific server type.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months