Also, I should remind everyone to use the
latest repository from Orbit (R20150519210750).
We've had one bug report that the latest from Orbit is not being used (Bug 468505)
and it's is unclear if there is a reason for it ... or if things will break
for anyone trying to use the latest from Orbit, along with things from
Mars (that happen to use the same logging fragment/framework where this
David M Williams/Raleigh/IBM@IBMUS
06/01/2015 03:13 AM
Status of Mars "repo report" results
One surprise, something we don't see often (don't think I ever have for
this repository) is that someone is contributing an "invalid jar"
to the repo ... normally this comes in the form of an invalid *jar.pack.gz,
but this time, the rare event, is it only the *.jar file. (No pack.gz file
is provided, or else the b3 aggregator would fail).
And it is for a new bundle from Orbit,
(And, yes, I checked Orbit, and it is correct in that repository).
that fail to verify (if any)
(which does not have much information, actually, but I documented in the
bug how to see more.
I have opened Bug
track this issue.
= = = == =
Other reports that deserve special attention (AFAIK, there are bugs opened
for these already).
- As far as "multiple versions of same plugin", I think that
report is looking fair (i.e. most cases are legitimate) but there is one
case that really stands out: Use of
org.apache.batik.dom at the 1.6.0 level. We went to a lot of effort to
replace that one with 1.6.1 (for security fix), so, please, get it out
of your builds and your own repositories, and
make sure Sim. Release repo does not have it. See List
of non-unique versions
Thanks to everyone who have been working hard to clean up previous issues.
My hope is that by RC3 we will be completely "clean". At least
for the reports mentioned here, which I take to be the most important,
but, by all means, please work on the others too!