Eclipse Community Forums: Oomph » Creating a Kepler based setup (httpclient 4.1 vs 4.2)

Help

Home

Home » Eclipse Projects » Oomph » Creating a Kepler based setup (httpclient 4.1 vs 4.2)

Show: Today's Messages :: Show Polls :: Message Navigator

Creating a Kepler based setup (httpclient 4.1 vs 4.2) [message #1385413]

Fri, 06 June 2014 09:24

Abel Hegedus

Messages: 197
Registered: September 2015

Senior Member

Hi,

I tried to create a setup which uses Kepler as a base but it seems that there are some plugins that are part of Eclipse which needs to be a higher version for Oomph to work.

Specifically, I get the following exception when the new Eclipse starts:

An internal error occurred during: "Setup check...".
java.lang.NoClassDefFoundError: org/apache/http/impl/cookie/DateParseException
	at org.eclipse.oomph.internal.setup.core.util.ECFURIHandlerImpl.createInputStream(ECFURIHandlerImpl.java:191)
	at org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360)
	at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1269)
[...standard EMF loading...]
	at org.eclipse.oomph.internal.setup.core.util.EMFUtil$1.getResource(EMFUtil.java:720)
[...standard EMF proxy resolution...]
	at org.eclipse.oomph.setup.impl.InstallationImpl.getProductVersion(InstallationImpl.java:79)
	at org.eclipse.oomph.internal.setup.core.SetupContext.getInstallation(SetupContext.java:308)
	at org.eclipse.oomph.internal.setup.core.SetupContext.createSelf(SetupContext.java:125)
	at org.eclipse.oomph.setup.ui.SetupUIPlugin.performStartup(SetupUIPlugin.java:168)
	at org.eclipse.oomph.setup.ui.SetupUIPlugin.access$3(SetupUIPlugin.java:147)
	at org.eclipse.oomph.setup.ui.SetupUIPlugin$1$1.run(SetupUIPlugin.java:116)
	at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: java.lang.ClassNotFoundException: org.apache.http.impl.cookie.DateParseException cannot be found by org.eclipse.oomph.setup.core_1.0.0.v20140605-1702

I checked and the manifest.mf of oomph.setup.core expects:

   org.apache.httpcomponents.httpclient;bundle-version="[4.2.0,5.0.0)";resolution:=optional,
   org.apache.httpcomponents.httpcore;bundle-version="[4.2.0,5.0.0)";resolution:=optional,

But in the new Eclipse, there is only:

   org.apache.httpcomponents.httpclient (4.1.3.v201209201135) "Apache HttpComponents HttpClient OSGi bundle" [Resolved]

Is there an exitsing way of dealing with this easily or is Kepler simply not compatible with the new Oomph (even though you can choose it as a product version)?

Thank you for any suggestions!

Report message to a moderator

Re: Creating a Kepler based setup (httpclient 4.1 vs 4.2) [message #1385420 is a reply to message #1385413]

Fri, 06 June 2014 10:27

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Hi Abel,

We contributed a few bug fixes to the most recent version of ECF, but I think we could work around those problems in
older versions. Please submit a bugzilla and I'll relax our constraints on the http components.

Please note that we've almost not tested Kepler compatibility, yet. If you encounter more trouble please let us know.

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 06.06.2014 11:24, schrieb Abel Hegedus:
> Hi,
>
> I tried to create a setup which uses Kepler as a base but it seems that there are some plugins that are part of
> Eclipse which needs to be a higher version for Oomph to work.
>
> Specifically, I get the following exception when the new Eclipse starts:
> An internal error occurred during: "Setup check...".
> java.lang.NoClassDefFoundError: org/apache/http/impl/cookie/DateParseException
> at org.eclipse.oomph.internal.setup.core.util.ECFURIHandlerImpl.createInputStream(ECFURIHandlerImpl.java:191)
> at
> org.eclipse.emf.ecore.resource.impl.ExtensibleURIConverterImpl.createInputStream(ExtensibleURIConverterImpl.java:360)
> at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1269)
> [...standard EMF loading...]
> at org.eclipse.oomph.internal.setup.core.util.EMFUtil$1.getResource(EMFUtil.java:720)
> [...standard EMF proxy resolution...]
> at org.eclipse.oomph.setup.impl.InstallationImpl.getProductVersion(InstallationImpl.java:79)
> at org.eclipse.oomph.internal.setup.core.SetupContext.getInstallation(SetupContext.java:308)
> at org.eclipse.oomph.internal.setup.core.SetupContext.createSelf(SetupContext.java:125)
> at org.eclipse.oomph.setup.ui.SetupUIPlugin.performStartup(SetupUIPlugin.java:168)
> at org.eclipse.oomph.setup.ui.SetupUIPlugin.access$3(SetupUIPlugin.java:147)
> at org.eclipse.oomph.setup.ui.SetupUIPlugin$1$1.run(SetupUIPlugin.java:116)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.apache.http.impl.cookie.DateParseException cannot be found by
> org.eclipse.oomph.setup.core_1.0.0.v20140605-1702
>
>
> I checked and the manifest.mf of oomph.setup.core expects:
>
> org.apache.httpcomponents.httpclient;bundle-version="[4.2.0,5.0.0)";resolution:=optional,
> org.apache.httpcomponents.httpcore;bundle-version="[4.2.0,5.0.0)";resolution:=optional,
>
> But in the new Eclipse, there is only:
>
> org.apache.httpcomponents.httpclient (4.1.3.v201209201135) "Apache HttpComponents HttpClient OSGi bundle" [Resolved]
>
> Is there an exitsing way of dealing with this easily or is Kepler simply not compatible with the new Oomph (even
> though you can choose it as a product version)?
>
> Thank you for any suggestions!

Cheers
/Eike

----
http://www.esc-net.de
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Report message to a moderator