Eclipse Community Forums: EMF » [CDO] missing org.eclipse.net4j.db.derby

Help

Home

Home » Modeling » EMF » [CDO] missing org.eclipse.net4j.db.derby

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

[CDO] missing org.eclipse.net4j.db.derby [message #514058]

Fri, 12 February 2010 10:37

Nicolas Bros

Messages: 49
Registered: July 2009

Member

Hi,

I am the release engineer for the MoDisco project.
MoDisco has a dependency on "org.eclipse.net4j.db.derby", but this plug-in is missing from the Helios update site, which makes the MoDisco build fail currently.

In "http://download.eclipse.org/releases/staging/", the source bundle "org.eclipse.net4j.db.derby.source" is present but not the "org.eclipse.net4j.db.derby" plug-in itself!

I think that is because "org.eclipse.net4j.db.derby" is not referenced by "org.eclipse.net4j.sdk".

Is that intended this way ? If not, could you fix this ?

Report message to a moderator

Re: [CDO] missing org.eclipse.net4j.db.derby [message #514070 is a reply to message #514058]

Fri, 12 February 2010 10:55

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Am 12.02.2010 11:37, schrieb Nicolas Bros:
> Hi,
>
> I am the release engineer for the MoDisco project.
> MoDisco has a dependency on "org.eclipse.net4j.db.derby", but this
> plug-in is missing from the Helios update site, which makes the
> MoDisco build fail currently.
>
> In "http://download.eclipse.org/releases/staging/", the source bundle
> "org.eclipse.net4j.db.derby.source" is present but not the
> "org.eclipse.net4j.db.derby" plug-in itself!
>
> I think that is because "org.eclipse.net4j.db.derby" is not referenced
> by "org.eclipse.net4j.sdk".
>
> Is that intended this way ? If not, could you fix this ?
I hope that it was unintentionally. I'll try to fix that for M6. Can you
please file a bugzilla to remind me?

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Cheers
/Eike

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

Report message to a moderator

Re: [CDO] missing org.eclipse.net4j.db.derby [message #514079 is a reply to message #514058]

Fri, 12 February 2010 11:29

Nicolas Bros

Messages: 49
Registered: July 2009

Member

Thanks. I have created bug 302693.

Report message to a moderator

Re: [CDO] missing org.eclipse.net4j.db.derby [message #514086 is a reply to message #514079]

Fri, 12 February 2010 06:58

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Am 12.02.2010 12:29, schrieb Nicolas Bros:
> Thanks. I have created
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=302693
BTW. I think you should be able to install the missing plugin from
/home/data/httpd/download.eclipse.org/modeling/emf/cdo/updat es/3.0

Eventually you need the 3rd party drivers from
http://net4j.sourceforge.net/update

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Cheers
/Eike

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

Report message to a moderator

Re: [CDO] missing org.eclipse.net4j.db.derby [message #521628 is a reply to message #514086]

Thu, 18 March 2010 10:51

Nicolas Bros

Messages: 49
Registered: July 2009

Member

Hi,

We still have some problems to configure the MoDisco releng build (with Athena).

We expect the releng to guarantee the quality of the MoDisco components which will be delivered in the Helios milestones. This guarantee includes the capability to use CDO to store MoDisco models. To realize this requirement, we compile and test the MoDisco components using the Helios "staging" update site.

But during our last exchange, we understood that "staging" is not enough to resolve the dependencies of MoDisco's unit tests using CDO: to run the tests we need a database connector (org.eclipse.net4j.db.derby) which is only available from http://download.eclipse.org/modeling/emf/cdo/updates/3.0/.

That's why we have configured the MoDisco releng to use the following update sites:
http://download.eclipse.org/releases/staging/
http://download.eclipse.org/modeling/emf/cdo/updates/3.0/
http://download.eclipse.org/tools/orbit/downloads/drops/S201 00308015149/updateSite/

But this configuration contains a risk: if "emf/cdo/updates/3.0" contains components which are more recent than the ones contained in "staging" then MoDisco releng will run tests for Helios Mx using CDO components that will not be provided in Helios Mx.

Do you agree with this? If yes, can you explain to us how to configure our releng to make sure to use the right version of CDO?

Report message to a moderator

Re: [CDO] missing org.eclipse.net4j.db.derby [message #521654 is a reply to message #521628]

Thu, 18 March 2010 11:58

Eike Stepper

Messages: 6682
Registered: July 2009

Senior Member

Hi Nicolas,

All this has changed recently. H2 and Derby should be fully included in
the Net4j DB and SDK features. They are now taken from Orbit. As the
staging build is broken for days I could not test it from there. But
from our own updates site it already works.

Cheers
/Eike

----
http://thegordian.blogspot.com
http://twitter.com/eikestepper

Am 18.03.2010 11:51, schrieb Nicolas Bros:
> Hi,
>
> We still have some problems to configure the MoDisco releng build
> (with Athena).
>
> We expect the releng to guarantee the quality of the MoDisco
> components which will be delivered in the Helios milestones. This
> guarantee includes the capability to use CDO to store MoDisco models.
> To realize this requirement, we compile and test the MoDisco
> components using the Helios "staging" update site.
>
> But during our last exchange, we understood that "staging" is not
> enough to resolve the dependencies of MoDisco's unit tests using CDO:
> to run the tests we need a database connector
> (org.eclipse.net4j.db.derby) which is only available from
> http://download.eclipse.org/modeling/emf/cdo/updates/3.0/
>
> That's why we have configured the MoDisco releng to use the following
> update sites:
> http://download.eclipse.org/releases/staging/
> http://download.eclipse.org/modeling/emf/cdo/updates/3.0/
> http://download.eclipse.org/tools/orbit/downloads/drops/S201 00308015149/updateSite/
>
>
> But this configuration contains a risk: if "emf/cdo/updates/3.0"
> contains components which are more recent than the ones contained in
> "staging" then MoDisco releng will run tests for Helios Mx using CDO
> components that will not be provided in Helios Mx.
>
> Do you agree with this? If yes, can you explain to us how to configure
> our releng to make sure to use the right version of CDO?

Cheers
/Eike

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

Report message to a moderator

Previous Topic:	copy in loop
Next Topic:	[EMF databinding] set binding problem

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Tue Apr 23 14:01:09 GMT 2024

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter