I would go for contrib + the dist jars of sfntly . Contrib's stuff is optional and it is ok to use java 1.6 . Eventually POI will switch to Java 1.6 and we will move your code to ooxml.
Yegor On Tue, Oct 15, 2013 at 2:00 AM, Andreas Beeker <[email protected]>wrote: > I don't know ... for my ISO-8859-1 requirements I didn't need them. You'll >>> find my repacked version under ... So it's an extra 280kb ... >>> >> Why did you need to repack sfntly? Was it repackaging only or you changed >> the source code too? >> I'm fine to include and distribute this library with POI but I'd like it >> to >> be an official release, not a fork. >> > > There were a few things I changed / bugged me: > - sfntly has @override annotations for interfaces which are a java 1.6 > feature. For our websphere environment, we needed a 1.5 library, so I've > removed all that annotations. I guess, its ok for a contrib to ask for a > new java environment ... but otherwise it doesn't fit to POIs 1.5 build > restriction. > - just checked the sources ... it's a pity, that sfntly still doesn't > support maven ... > - just searched for an official binary release of sfntly.jar + > sfntly-eotconverter.jar ... couldn't find one (sfntly.jar alone is included > in a few google code projects) > > So what you would you prefer? > - a seperate build in the contrib + .txt-instructions how to get sfntly > and optionally downgrade it to 1.5 if neccessary > - contrib + the dist jars of sfntly (java 1.6) > - the sources in the scratchpad area and build-only jars of sfntly (java > 1.5) > - ... > > Andi. > > > ------------------------------**------------------------------**--------- > To unsubscribe, e-mail: > [email protected].**org<[email protected]> > For additional commands, e-mail: [email protected] > >
