I would like to propose adding support for Java 7’s java.nio.file.Path as an alternative to those methods in the API that deal with a java.io.File.
This is pretty trivial for File as a param, as new overloaded methods/constructors can be added that accept a Path. A few questions arise: 1) What can we do with methods returning a File? e.g. TemporaryResources.createTemporaryFile, TikaInputStream.getFile. Should we break compatibility and encourage (=force) users to change their code (Note that since they all use Java 7 now, the change is minimal by adding .toFile() to the result), or create new methods with different names (confusing)? 2) Should we deprecate the old methods accepting a File, or delete them? I’m ready to open an issue and provide patches. *Yaniv Kunda* Technical Lead yaniv.ku...@answers.com *p* +972 (3) 7661819 *m* +972 (54) 4644456 [image: Webcollage by Answers] www.answers.com/webcollage -- This email communication (including any attachments) contains information from Answers Corporation or its affiliates that is confidential and may be privileged. The information contained herein is intended only for the use of the addressee(s) named above. If you are not the intended recipient (or the agent responsible to deliver it to the intended recipient), you are hereby notified that any dissemination, distribution, use, or copying of this communication is strictly prohibited. If you have received this email in error, please immediately reply to sender, delete the message and destroy all copies of it. If you have questions, please email le...@answers.com. If you wish to unsubscribe to commercial emails from Answers and its affiliates, please go to the Answers Subscription Center http://campaigns.answers.com/subscriptions to opt out. Thank you.
