We constantly answer this. Basically the answer is "whatever your unit tests say". We're all fanatics...just look: http://jakarta.apache.org/poi/junit/index.html (don't worry those are from the HEAD and not 2.0 branch)
I almost always have more confidence in the latest from CVS because it has MORE unit tests. When developing an application, I write a test suite that covers what I expect my application will do. Thus I know that the release I'm using of WHATEVER software or library will work. Then I can use the HEAD, a 2 year old release, whatever....this is fearless programming. If I know the I wrote a good test...I know the software will work. Now if you want us to be real helpful...you have to work near the head. Not that we won't help but that we don't remember what we did a year ago as well as we know what we're working on RIGHT NOW. So if you work near the head (atm, I mean at the head of the 2.0 branch not the "HEAD" in cvs), with good unit tests, you'll get really nice support and have good confidence in what you're doing. If you go old school and do late adoption with no tests, rush to the finish...POI is the least of your worries :-) I learned all this from working on this project. I used to think this was a stupid philosophy until I discovered that the unit tested code was the code that always worked...my un-tested code always broke. -Andy On 10/9/03 7:52 AM, "Morten" <[EMAIL PROTECTED]> wrote: > > Hi, > > Are there any reasons at all to use 1.5.1 rather than 2.0-pre3? > > Thanks, > > Morten > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- Andrew C. Oliver http://www.superlinksoftware.com/poi.jsp Custom enhancements and Commercial Implementation for Jakarta POI http://jakarta.apache.org/poi For Java and Excel, Got POI? The views expressed in this email are those of the author and are almost definitely not shared by the Apache Software Foundation, its board or its general membership. In fact they probably most definitively disagree with everything espoused in the above email. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
