Should a new project be tied to jdk 1.7?

Question

Java

The title basically says it all. There are quite a lot of amenities in jdk 1.7 that are already tired of copy-pasting from project to project (specifically, now I need to work with files and paths - java.nio.file).
I need to write a small library and I think to make jdk 1.7 the minimum requirement. It will not be used for android.
On the one hand, jdk 6 is in an end-of-life state, but a lot of projects use it.
True, in the end I write for my own needs, and whether someone else will use it does not bother me much).

Answer 1

in such conditions, it’s definitely worth it, there are several rock projects for 1.7 in production, I don’t see any problems

Answer 2

Similarly, there is a project that was on 1.6 for a long time, just a couple of months ago I started using 1.7 chips, now it works on 1.7 Java in production.