Fine with me. Matt
On Tue, May 22, 2018 at 1:00 PM, Mark Struberg <[email protected]> wrote: > How about switching bv2 to master and master to bval-1.1.x ? > > > LieGrue, > strub > > > Am 01.05.2018 um 20:32 schrieb Romain Manni-Bucau <[email protected] > >: > > > > Sounds good > > > > Maybe just bval-impl then. > > > > Le 1 mai 2018 19:51, "Matt Benson" <[email protected]> a écrit : > > > >> On Tue, May 1, 2018 at 12:44 PM, Romain Manni-Bucau < > [email protected] > >>> > >> wrote: > >> > >>> Le 1 mai 2018 18:53, "Matt Benson" <[email protected]> a écrit : > >>> > >>> Hi all, > >>> I have upgraded commons-weaver to be compatible with Java 8 and > >> enhanced > >>> the privilizer module to handle method references. Our bv2 branch can > now > >>> successfully run its "sec" profile on Linux. Since it works there but > no > >>> longer works on Windows, I expect the reason is policy file platform > >>> weirdness. Anybody who wants to work on that is welcome but I'm not > >>> considering it to be a blocker. > >>> > >>> The Hibernate guys have released the 2.0.3.Final version of the TCK > >> which > >>> included several fixes and our branch passes this version of the TCK. > >>> > >>> As I see it our remaining tasks are: > >>> * rename and repackage the bval-jsr module > >>> > >>> > >>> To? I renamed to jsr for bval 1.1 to avoid future renaming so hope to > >> stay > >>> stable here > >>> > >> > >> Remember that I merged the remaining needed code from bval-core into > >> bval-jsr as part of the decision to drop the legacy support. Apache > BVal is > >> now focused on Bean Validation in deed as in word. I considered renaming > >> the module back to bval-core, but I think it's more appropriate to > simply > >> name it "bval". > >> > >> > >>> * add OSGI manifest info to that module and remove the bundle module > >>> > >>> > >>> Bundle was more a shade, we can have both pby > >>> > >> > >> With the removal of the erstwhile bval-core, a bundle shading in > bval-jsr > >> should be equivalent to bval-jsr + osgi. > >> > >> Matt > >> > >> > >>> * see that commons-weaver 1.4 is released in the Commons community > >>> > >>> We can discuss these in more detail in separate threads, but does > anyone > >>> else know of some other critical task we should be considering? > >>> > >>> > >>> Nthg, just let it go out and congrats for your work! > >>> > >>> > >>> Thanks, > >>> Matt > >>> > >> > >
