Bertrand Delacretaz wrote:
> ...Also what if the release of Cocoon I'm using has an old version of a
> jar file and my project absolutely requires the latest version. Should
> anything I put into the project lib directory override the Cocoon
> release version?...
As is, it doesn't, I think you'll get a mix of versions if you do this. If
you want to replace Cocoon jars I think you'll have to maintain lists of
files to remove, or bug us to upgrade the jars in the distribution.
Thanks for the help.
Mmm... I think I'll have to do something along those lines. I also found
myself enabling some Cocoon blocks I didn't actually need just so the core
library I did want was in the classpath (Lucene for example).
The more I think about it the more I realize how difficult this is. You
can't simply say "use this jar file in preference to any other" because the
other jar files may be named differently yet contain the same classes.
Regards,
David Legg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
