> Totally different topic. I just had to dig up the 'correct' jars for a > project (Velosurf) yesterday. It would have saved me a lot of time if I > had a list of the minimum req'ts.
Yes, thanks on your feedback on the velosurf list, Tim. But the readme for the sample says you have to copy the libs from the /velosurf/lib directory, which contains all the needed jars - and in fact, those jars are needed by veltools, not Velosurf itself. CloD ----- Original Message ----- From: "Tim Colson" <[EMAIL PROTECTED]> To: "'Velocity Developers List'" <[EMAIL PROTECTED]> Sent: Thursday, April 15, 2004 5:35 PM Subject: RE: 1.4 dependency jars > > [Geir] There's been no change in requirements since we did this in > 1.2... > > what's the problem? > Totally different topic. I just had to dig up the 'correct' jars for a > project (Velosurf) yesterday. It would have saved me a lot of time if I > had a list of the minimum req'ts. > > So I can empathize with Mike's suggestion, but I like my verbiage/format > better. :-) > > Timo suggested version for the doc: > -------------------------------------------------- > 1) velocity-<version>.jar : Velocity jar which does NOT > contain required dependencies. This enables a project to use > different jar versions without fear of collision. > > Minimum requirements: > Jakarta Commons Collections (commons-collections.jar -- 2.1 or higher) > Jakarta Avalon Logkit (logkit-1.0.1.jar -- 1.0.1 or higher) > Jakarta ORO (oro.jar -- ?no idea? or higher) > > NOTE: These jars are included in the distribution -- in the build/lib > directory, but may of course be obtained from the respective project > sites. > -------------------------------------------------- > > -- Timo > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
