> Apart from the bugfixing we've added better support for 7z compression > methods - you can now chose a stack of more than one method when writing > (this has always been possible when reading), pass options to the > methods and use different configurations per entry. The core of this > are the new get/setContentMethods methods in SevenZOutpuzFile and > SevenZArchiveEntry along with the new SevenZMethodConfiguration class.
To summarize some discussion from IRC back to the list: The main change is this one <http://svn.apache.org/viewvc/commons/proper/compress/trunk/src/main/java/org/apache/commons/compress/archivers/sevenz/SevenZArchiveEntry.java?r1=1552756&r2=1571923> with some later variations. The Iterable as argument to the setter looks inconvenient and a varargs signature may be more user friendly - in particular in a use-case where you only want to pass in a single "method". Personally I prefer to keep getter and setter symmetric and don't like the idea of copying things around in order to not expose state if the API was array based. The inconvenience is just an extra Arrays.asList for the user. But I don't have any strong feelings either way. The API is not going to be used much as most people will read archives or create archives with just a single method. The major use-case I envision is copying entries from one archive to another and keeping the same methods. Any thoughts? Stefan --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
