I'm not sure I understand all the issues ... but, will answer
best as I can ... then maybe you could ask more questions.
> ... Should CDO avoid repacking the jars from Orbit?
do you literally mean "repack"? or pack? In
generally, it is best (maybe essential) to avoid "repacking"
(conditioning) jars, if they already have been, especially if already signed.
But, yes, projects are expected to pack (pack200) files
they get and redistribute from Orbit.
> Should MoDisco build using the Orbit jars from the
CDO update site?
Yes, if MoDisco needs it (and has a CQ for it :). If you
need it independently of CDO then you should likely get, package, and distribute
it yourself. If you need it just because CDO does (and you need CDO), then
it is fine to get from CDOs distribution. (You still need a CQ, in both
cases, if you distribute it).
> What about when the same Orbit jar is required by
several different projects?
This is pretty common ... contents should be exactly the
It almost sounds like your metadata is being "blended"
so that what is a packed jar on CDOs site is expected to be a packed jar
everywhere, but I do no think you can make assumptions like that ... it
would vary repo by repo.
So, hope these answers give some ideas of what to look
at, or what to ask next. Apologies if I am missing your point.
Nicolas Bros <nbros@xxxxxxxxxxxxxxxx>
09/08/2011 04:53 AM
error with org.apache.derby jar.pack.gz expected
I interpret this as meaning that org.apache.derby is
expected to be packed. So I believe this is the cause for the error.
Apparently CDO packs the jar from Orbit in its own update
site : <downloads>/modeling/emf/cdo/drops/S20110907-0210/plugins/org.apache.derby_10.5.1.1_201105231903.jar.pack.gz
I'm not sure what is the right way to fix this. Should
CDO avoid repacking the jars from Orbit? Should MoDisco build using the
Orbit jars from the CDO update site? What about when the same Orbit jar
is required by several different projects?