Build systems are boring. Changing build systems is disruptive. There is no reason to do it unless we have a solid thing that it would make easier, better, faster for building POI.
Instead, if you want to help, how about profiling POI, reducing memory consumption? How about prototyping Random Access files? How about going through and finding any place where we do something boneheaded like "new String()" and creating a smart system for handling Encoding? I'm not trying to discourage you from contributing but just saying that switching out the build system is probably the least desirable way you could contribute. The build works. It is pretty fast (at least on my box) and generates our artifacts. This is plenty reason not to disrupt things. -Andy On Sun, Aug 24, 2008 at 6:03 PM, Dayo Egbetola <[EMAIL PROTECTED]> wrote: > hi everyone, > > I'm new to the mailing list and would like to contribute. At the > moment, i see that the building of the code uses ant even though build > technologies like ivy and maven exist out there. Admittedly POI was in > existence before these came along but i wanted to find out if there > any plans to move POI to use Mave/Ivy? Has anyone looked into what it > would take to do it? Are there any reasons why using Maven would not > be good idea for POI? > > Please share your thoughts > > regards > > Dayo > > --------------------------------------------------------------------- > 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]
