I believe ValidationAPI is part of the javacard cluster - or at least it was developed there - so, that means without the javacard modules, there is probably nothing that depends on it.
It is just a wrapper for this - https://github.com/timboudreau/simplevalidation - originally on java.net, I moved it to github since that. And just a reminder: "nobody maintaining" something that works is a non-problem - software *can* actually be finished, if you carve problems into small enough and well-defined enough chunks (and you and everyone should). Lack of maintenance might mean neglect, but it also might mean it simply works. But in this case it has probably not reached a state of perfection yet, and it *is* maintained (if I had it to write again, a bunch of it could be done much more cleanly taking advantage of lambdas). -Tim On Thu, Sep 19, 2019 at 5:33 AM Andreas Sewe <s...@cqse.eu> wrote: > Eric Barboni wrote: > > Using org.netbeans.external: ValidationAPI :RELEASE90 should be enough. > It is just a jar. > > Thanks for digging into this, Eric. > > Turns out that ValidationAPI RELEASE82 is byte-for-byte identical to > RELEASE90, RELEASE100, and RELEASE110. So it doesn't really matter which > version I pick. > > It's a bit worrying, though, that apparently no-one maintains that API > anymore. But unless it suddenly becomes incompatible with Java Umpteen > (not impossible, given the speed with which Java is changing nowadays), > I can live with this. > > Best wishes, > > Andreas > > -- > Dr. Andreas Sewe | s...@cqse.eu | +49 152 56342856 > CQSE GmbH | Centa-Hafenbraedl-Strasse 59 | 81249 Muenchen | www.cqse.eu > Amtsgericht Muenchen | HRB 177678 | GF: F. Deissenboeck, M. Feilkas > > -- http://timboudreau.com
