I would personally like to see the project mavenized. Maven absolutely blows ant away as far as project organization goes.
I'm +1 for any refactoring that enforces simplicity, and cohesiveness with other Apache projects. The more we are like, say the jakarta-commons projects, the easier it will be for users to understand ours. The negative part of moving to maven- it'll be a little work. I *really* think/hope that any effort you put in will be towards getting the CVS head consistent and as bug free as possible, so we can release. Mavenizing is not in that spirit. I was working with the test-all on windows running the standalone server. I feel that making the current tests work for all drivers is our *highest* priority. Thoughts? -Kevin Ross ------------------------------------------------ On Fri, 01 Aug 2003 14:51:23 +1000, "Kevin O'Neill" <[EMAIL PROTECTED]> wrote: > On Fri, 01 Aug 2003 00:34:01 -0400, Vadim Gritsenko wrote: > > > Hi y'all, > > > > I'd like to update build system a bit. Including: > > * Move ant to tools/bin and tools/lib. * Update ant to 1.5.3 > > * Update build.bat and build.sh accordingly > > Do we need a build.sh / build.bat? At the moment I build using ant > <target> > > > And some other minor changes. Also, I find it convinient to group all the > > licenses into separate directory, 'legal'. Any objections? > > There's an old post by Kevin Ross about reorganising the repository. I > personaly don't care which way. Less changes are good for me though ... I > update over a modem :(. > > > PS Are we keeping track of changes in the status.xml? It's kind of empy as > > it is... > > I'll start as soon as my apache account is activated :). > > -k. >
