On Thu, 19 Jan 2006, Jörg Heinicke <[EMAIL PROTECTED]> wrote: > I wonder why so many projects depend on *our* packaged jmock.
Ahh, for historical reasons. I was experimenting with building jmock and it simply will never work (a backwards incomatible change in JUnit in the dead 3.8.x branch made after the release of 3.8.1 together with a very very very old version of ASM being required). As a stopgap I made Cocoon depend on its own version of jmock again, so you could build. Then excalibur needed jmock and I simply reused your version instead of installing it separately. In fact the huge number of projects stems from excalibur not building (transitive dependencies). > At least Cocoon has removed it from its repository and it must > probably fixed/added somewhere else now Done. Stefan