[JBoss JIRA] (TOOLSDOC-694) Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-694?page=com.atlassian.jira.plug... ]
Len DiMaggio edited comment on TOOLSDOC-694 at 12/9/15 10:36 AM:
-----------------------------------------------------------------
The doc is misleading as it implies that an "update" can be performed when in reality, a new install of JBDS is needed.
I think that the important text that we should include is:
This Red Hat JBoss Developer Studio 9.0.0 Installer includes everything you need to install JBoss Developer Studio, as well as a copy of Red Hat JBoss Enterprise Application Platform 6.4.0.
This patched version of Red Hat JBoss Enterprise Application Platform 6.4.0 includes this fix:
BZ-1281963 - CVE-2015-7501 Apache commons-collections: InvokerTransformer code execution during deserialisation
https://access.redhat.com/jbossnetwork/restricted/softwareDetail.html?sof...
was (Author: ldimaggio):
The doc is misleading as it implies that an "update" can be performed when in reality, a new install of JBDS is needed.
I think that the important text that we should include is:
This Red Hat JBoss Developer Studio 9.0.0 Installer includes everything you need to install JBoss Developer Studio, as well as a copy of Red Hat JBoss Enterprise Application Platform 6.4.0.
This patched version of Red Hat JBoss Enterprise Application Platform 6.4.0 includes this fix:
BZ-1281963 - CVE-2015-7501 Apache commons-collections: InvokerTransformer code execution during deserialisation
> Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article
> --------------------------------------------------------------------
>
> Key: TOOLSDOC-694
> URL: https://issues.jboss.org/browse/TOOLSDOC-694
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Reporter: Supriya Bharadwaj
> Assignee: Martin Malina
>
> [~mmalina], you may find the article at > https://docs.google.com/document/d/1BiZV7vMatYblmv73WJzNqUrmzF2ah011pwEqK...
> As discussed, please feel free to recommend deletions/additions/modifications to the article so that we can come up with the most appropriate content for the users.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21215) IUs missing from snapshot update site while site is being published
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21215 at 12/9/15 10:36 AM:
--------------------------------------------------------------
If you happen to hit the update site WHILE it's being replaced, or hit it BEFORE a replacement to read metadata, then start the update WHILE it's being replaced, there's nothing we can do to make the internet work a different way. Either the files are there, or they're not.
But you can always use the "composite of the last few aggregates" if you want something more stable. That's what we use in our jobs.
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
Curiously, the last two builds have a different set of IUs that the ones your system requested:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
{code}
org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151208-0926-B67.jar
{code}
instead of org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151205-0132-B64
Looks like you were reading from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... or an even older build.
But you created this issue only 3 hours ago, so I have no idea why you'd be seeing a *34 hour* old CI build in http://download.jboss.org/jbosstools/mars/snapshots/updates/ (or the linked site, http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ ) when there have been several builds since then.
And no, composite site job won't save you from obsolete metadata in your Eclipse's cache. I suspect the problem here is at your end.
was (Author: nickboldt):
If you happen to hit the update site WHILE it's being replaced, or hit it BEFORE a replacement to read metadata, then start the update WHILE it's being replaced, there's nothing we can do to make the internet work a different way. Either the files are there, or they're not.
But you can always use the "composite of the last few aggregates" if you want something more stable. That's what we use in our jobs.
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
Curiously, the last two builds have a different set of IUs that the ones your system requested:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
{code}
org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151208-0926-B67.jar
{code}
instead of org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151205-0132-B64
Looks like you were reading from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... or an even older build.
But you created this issue only 3 hours ago, so I have no idea why you'd be seeing a 10 hour old CI build in http://download.jboss.org/jbosstools/mars/snapshots/updates/ (or the linked site, http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ ).
And no, composite site job won't save you from obsolete metadata in your Eclipse's cache. I suspect the problem here is at your end.
> IUs missing from snapshot update site while site is being published
> -------------------------------------------------------------------
>
> Key: JBIDE-21215
> URL: https://issues.jboss.org/browse/JBIDE-21215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
>
> running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/
> I get this error:
> {quote}
> An error occurred while collecting items to be installed
> session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21215) IUs missing from snapshot update site while site is being published
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21215?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21215:
------------------------------------
If you happen to hit the update site WHILE it's being replaced, or hit it BEFORE a replacement to read metadata, then start the update WHILE it's being replaced, there's nothing we can do to make the internet work a different way. Either the files are there, or they're not.
But you can always use the "composite of the last few aggregates" if you want something more stable. That's what we use in our jobs.
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
Curiously, the last two builds have a different set of IUs that the ones your system requested:
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui...
{code}
org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151208-0926-B67.jar
{code}
instead of org.jboss.ide.eclipse.as.management.wildfly9_3.1.1.Beta1-v20151205-0132-B64
Looks like you were reading from http://download.jboss.org/jbosstools/mars/snapshots/builds/jbosstools-bui... or an even older build.
But you created this issue only 3 hours ago, so I have no idea why you'd be seeing a 10 hour old CI build in http://download.jboss.org/jbosstools/mars/snapshots/updates/ (or the linked site, http://download.jboss.org/jbosstools/mars/snapshots/updates/core/4.3.mars/ ).
And no, composite site job won't save you from obsolete metadata in your Eclipse's cache. I suspect the problem here is at your end.
> IUs missing from snapshot update site while site is being published
> -------------------------------------------------------------------
>
> Key: JBIDE-21215
> URL: https://issues.jboss.org/browse/JBIDE-21215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Reporter: Max Rydahl Andersen
>
> running updates from: http://download.jboss.org/jbosstools/mars/snapshots/updates/
> I get this error:
> {quote}
> An error occurred while collecting items to be installed
> session context was:(profile=_Users_max_products_eclipse_jee-mars3_Eclipse.app_Contents_Eclipse, phase=org.eclipse.equinox.internal.p2.engine.phases.Collect, operand=, action=).
> No repository found containing: osgi.bundle,org.jboss.tools.common,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.el.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.jdt.debug.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.resref.core,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.text.xml,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.ui,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.common.validation,3.7.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.checkup,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.foundation.ui,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.cdk.server,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.common.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.egit.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.client,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.core,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.express.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.openshift.ui,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.core,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.runtime.ui,3.1.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.stacks.core,1.2.1.Beta1-v20151204-0542-B55
> No repository found containing: osgi.bundle,org.jboss.tools.usage,2.1.1.Beta1-v20151204-0542-B55
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.cdk.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.express.feature,3.1.0.Beta1-v20151205-0342-B106
> No repository found containing: org.eclipse.update.feature,org.jboss.tools.openshift.feature,3.1.0.Beta1-v20151205-0342-B106
> {quote}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (TOOLSDOC-694) Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-694?page=com.atlassian.jira.plug... ]
Len DiMaggio commented on TOOLSDOC-694:
---------------------------------------
The doc is misleading as it implies that an "update" can be performed when in reality, a new install of JBDS is needed.
I think that the important text that we should include is:
This Red Hat JBoss Developer Studio 9.0.0 Installer includes everything you need to install JBoss Developer Studio, as well as a copy of Red Hat JBoss Enterprise Application Platform 6.4.0.
This patched version of Red Hat JBoss Enterprise Application Platform 6.4.0 includes this fix:
BZ-1281963 - CVE-2015-7501 Apache commons-collections: InvokerTransformer code execution during deserialisation
> Review: Update Red Hat JBDS 9.0.0 Containing Patched EAP 6.4 article
> --------------------------------------------------------------------
>
> Key: TOOLSDOC-694
> URL: https://issues.jboss.org/browse/TOOLSDOC-694
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Feature Request
> Reporter: Supriya Bharadwaj
> Assignee: Martin Malina
>
> [~mmalina], you may find the article at > https://docs.google.com/document/d/1BiZV7vMatYblmv73WJzNqUrmzF2ah011pwEqK...
> As discussed, please feel free to recommend deletions/additions/modifications to the article so that we can come up with the most appropriate content for the users.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21207) While typing path to local template, temporarily invalid path cause several errors and pops up reporting dialog
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21207?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21207:
------------------------------------------
fixed in commit [d8538e2616d162a96eb7f6a9c7408547aa50ff07|https://github.com/jbosstools/jb...]
> While typing path to local template, temporarily invalid path cause several errors and pops up reporting dialog
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21207
> URL: https://issues.jboss.org/browse/JBIDE-21207
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Assignee: Fred Bricon
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta1
>
> Attachments: error_path_validation.png
>
>
> In OpenShift New Application wizard on first wizard page where path to local template is supposed to be filled in occurs several errors while typing this value. Validator shows error correctly, but there is error of validation shown in error log several times. Example of an error and its stacktrace
> {code}
> Unhandled exception: com.openshift.restclient.OpenShiftException: Could not find the file "/" to upload
> java.lang.RuntimeException: com.openshift.restclient.OpenShiftException: Could not find the file "/" to upload
> 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.swt.WidgetListener.handleEvent(WidgetListener.java:56)
> 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:1329)
> 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:279)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:34)
> 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.GeneratedMethodAccessor91.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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:1329)
> 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:497)
> 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.OpenShiftException: Could not find the file "/" to upload
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalTemplate(NewApplicationWizardModel.java:119)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.updateSelectedTemplate(NewApplicationWizardModel.java:96)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.update(NewApplicationWizardModel.java:88)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.setLocalTemplateFileName(NewApplicationWizardModel.java:325)
> at sun.reflect.GeneratedMethodAccessor80.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59)
> ... 92 more
> Caused by: java.io.FileNotFoundException: / (Is a directory)
> at java.io.FileInputStream.open0(Native Method)
> at java.io.FileInputStream.open(FileInputStream.java:195)
> at java.io.FileInputStream.<init>(FileInputStream.java:138)
> at java.io.FileInputStream.<init>(FileInputStream.java:93)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.createInputStream(NewApplicationWizardModel.java:320)
> at org.jboss.tools.openshift.internal.ui.wizard.newapp.NewApplicationWizardModel.getLocalTemplate(NewApplicationWizardModel.java:117)
> ... 99 more
> {code}
> It's caused when typing path to local OpenShift template in the text widget, because this path is temporarily invalid (it's valid once its written whole). Sometimes also an error reporting dialog is shown. See following screenshot:
> !error_path_validation.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months