>>> Is anyone else hitting the above error when trying to run the latest
>>> As far as I can tell, it only happens on Windows, but I can't figure
>> I had seen this right after upgrading to the new Avalon release, I
>> think. I think it is because at one point we built some Avalon
>> components/framework/logkit for use in Keel using the Avalon dev
>> tree, and put them up on the Keel Maven repo. Eventually the
>> component got changed, but released using the same version, so Maven
>> doesn't know to download the "improved" :-) version. Try deleting
>> all the avalon/excalibur dirs from your Maven repo and rebuilding.
> One more thing, I am not sure, but you may have to rebuild all your
> Keel components, not just the final app.
Someday I'll get all my thoughts in one email. Until then:
We probably ought to delete the Avalon JARs from the Keel Maven repo. I
have been using the following property in my build.properties, making
Keel go after apache and ibiblio.