On Tue, 1 Oct 2002 17:18, Johan Sj�berg wrote: > > Any reliable/stable jars/products should not be stored in CVS but are > > downloaded from their download site. MX4J is already downloaded. We > > should be downloading Wrapper and requiring it for our build but no ones > > got around to that yet. > > No prob, just some simple ant tasks for the wrapper.
kool. > > For things that are only used in building the product we should place > > them in tools/ subdirectory. > > E.g. the setup compiler in this case. There is a small problem though. > At least with inno-setup. It is distributed as a windows setup EXE so it > can't be downloaded and extracted. I think that at least the > command-line compiler, some DLLs and the english language files would > have to be included in CVS for this to run really smoothly. > > OK, I know, if it is installed on _the_ windows build machine its dir > could be included in ant.properties. BUT, that would make building a > full dist even more cumbersome than now... this is probably the way to > start though. yep. > > If the jars are part of the server then they should be > > placed in the lib/container directory. If the jars are used by hosted > > applications aswell as the container they should be put in lib/ > > directory. > > OK, the wrapper is part of the server, but not needed by the rest of it. > All files are now in ./bin, but as Leif pointed out this is not so clean. We could probably move the jars into bin/lib, native files into bin/native/win32/ or bin/native/linux/ or whatever - I presume it is just modifying configuration files to get that going. -- Cheers, Peter Donald ------------------------------------------------------------ militant agnostic: i don't know, and you don't know either. ------------------------------------------------------------ -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
