I have a project that uses poi, and I have been releasing it in 2 jars since poi 3.2. One for my code and one for poi. I just tried upgrading from poi 3.6 to 3.8, and the code would no longer run. Apparently, poi3.8 introduced a dependency on Apache commons-codec in HSSFWorkbook.addPicture. It's not a hard dependency - the code runs until I call addPicture, then I get a 'class not found' error.
I was able to get it running again, by downloading commons-codec.jar and including it in my classpath. But I really don't like having to change release procedures for the thing to require new libraries. (I'm also not nuts about having had to figure this out from cryptic run-time error messages - I don't see anything on the POI website or javadocs that mentions this dependency). For yucks, I tried 'unjar'ing both poi.jar and commons-codec and re-jarring everything into a single jar, and calling *that* poi.jar (i.e. poi, and all it's dependencies). That works and allows me to stick to my same 2 jar release procedure. The question is, is that inadvisable? Or is it a common thing to do? I don't think I want to package the poi and commons-codec stuff together with my own jar. That would be overkill. Opinions? --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
