> If poi is important to you, you have two options: > > 1) read the documentation, use google to search the mailing lists etc, > and hopefully find your answer. If it looks like you really do have > a bug in the bit of poi you're using, write a simple junit unit test > that highlights the problem, and upload it to bugzilla. > (The quality of your bug report is highly likely to affect the speed > with which a volunteer developer gets around to fixing it) > 2) Pay a consultant / take out a support contract, and have someone you're > paying help you + resolve any bugs you hit
3) Look at the source code. I've had to do this on occasion with POI and it's all pretty straightforward and you can understand exactly where a problem originates and usually how to work around it. - Filip --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
