And we're working on just such a list of the dependencies. That is one benefit of moving the jars out of SVN. I took the approach that the Struts build uses. The build script clearly lists the depencies and the version numbers required.
Of course we could have that without removing the jars from SVN too. But its 100% essential if we don't supply the jars and so now we have it. Both sides should be happy on this point :-) sean On 6/27/05, ir. ing. Jan Dockx <[EMAIL PROTECTED]> wrote: > > On 25 Jun 2005, at 20:43, Craig McClanahan wrote: > > > > > For the record, I am absolutely and totally -1 on including JAR files > > in the source code repository of any Apache project that I work on. > > Including them in a binary distribution, of course, is a totally > > different animal. > > > > Craig > > > > > > Even then. (see previous post). In my opinion (for as much as that of a > user counts), only end-user products should contain all dependencies. > Libraries should never, but instead list the dependencies with all > needed information, including what each dependency is needed for. > > > Met vriendelijke groeten, > > Jan Dockx > > PeopleWare NV - Head Office > Cdt.Weynsstraat 85 > B-2660 Hoboken > Tel: +32 3 448.33.38 > Fax: +32 3 448.32.66 > > PeopleWare NV - Branch Office Geel > Kleinhoefstraat 5 > B-2440 Geel > Tel: +32 14 57.00.90 > Fax: +32 14 58.13.25 > > http://www.peopleware.be/ > http://www.mobileware.be/ > > >
