Andrew Niefer wrote:
If there is a problem
with the siteOptimizer,
it is simply that it does not handle corrupt input and quietly leaves
size
0 files instead of failing outright.
The open question is this:
1) Are the .jar files produced by
individual
teams valid at the end of their build? (I expect these are already
condition and signed?)
I'm assuming they are because the various teams use them as inputs to
their testing processes, but I don't actually know. Is there any easy
way for me to add a ant task to check their validity?
2) Are the .jar files
used as input
to the Europa build bitwise the same as the jars in (1).
The Europa-matic build has two steps:
- Run the "-application org.eclipse.update.core.standaloneUpdate"
to gather the jars from all the project update sites into a single
europa update site.
- Run the "-application org.eclipse.update.core.siteOptimizer" over
those jars to pack them.
Is this still the case? If so
then the bug is likely in standaloneUpdate and somehow missed getting
raised.
That could be - the Europa-matic is just using these
org.eclipse.update.core.... application to do its work.
--
[end of message]
|
