Agreed, but updating to a Spring minor version and the OSGI config also seems more than a patch fix?
On Mon, Feb 4, 2019 at 11:25 AM Les Hazlewood <[email protected]> wrote: > Per semantic versioning, major and minor versions should only be > incremented if there is a change/addition to the API exposed to > application developers. If we're just changing pom.xml files, a point > revision seems more appropriate, no? > > On Mon, Feb 4, 2019 at 11:22 AM Brian Demers <[email protected]> > wrote: > > > > +1 > > we might want to bump the Shiro version to 1.5.0 it sounds like we have > > Spring version update plus all of the OSGI stuff, > > Thoughts? > > > > On Sun, Feb 3, 2019 at 1:38 AM Jean-Baptiste Onofré <[email protected]> > wrote: > > > > > +1 > > > > > > it sounds good to me. > > > > > > Regards > > > JB > > > > > > On 03/02/2019 07:37, Francois Papon wrote: > > > > Hi, > > > > > > > > I have a local branch with an upgrade of Spring to 4.3.22 wich is > > > > compatible with JDK 6-8. > > > > > > > > All tests passed and I think we could include this upgrade to the > next > > > > 1.4.1 Shiro release. > > > > > > > > @Brian : we will be ok with owasp check :) > > > > > > > > Thoughts? > > > > > > > > Regards, > > > > > > > > > > -- > > > Jean-Baptiste Onofré > > > [email protected] > > > http://blog.nanthrax.net > > > Talend - http://www.talend.com > > > >
