I just imported Cocoon into Eclipse, so I could have a decent tool-- JEdit is ok, but it is no IDE replacement. One of the first things I noticed is that we have duplicate entries for the same JARs. What's worse is that some of thsoe entries are for different versions.
Take a look at the JARs in sandbox and the JARs in blocks. There are several snapshot releases of JARs (with the date they were built), but an older version is in sandbox while a newer version is in blocks.
I don't know where you got that from, but I'm pretty positive there are no jar duplicates in our CVS tree. The problem might be the build target that builds the eclipse project file.
That's pretty sloppy.
It is, that's why I spent time to make sure we didn't.
Can we pull these JARs from a central repository like Maven's ibiblio location?
No, not yet. Too many things are happening on that side. It would be again building on sand.
That would ease the stress on the CVS server (downloading and trying to keep all these JARs up to date). It would also make sure that the same version of each JAR is used in each location.
They are, trust me.
-- Stefano Mazzocchi <[EMAIL PROTECTED]> Pluralitas non est ponenda sine necessitate [William of Ockham] --------------------------------------------------------------------
