Is 1.7.x relegated to just security fixes now? I'm just curious how likely we are to see a 1.7.2 without some critical vulnerability being disclosed..
On Fri, Mar 13, 2015 at 2:01 AM, Romain Manni-Bucau <[email protected]> wrote: > Sure > Le 13 mars 2015 01:37, "jieryn" <[email protected]> a écrit : > >> Will it make it into 1.7.2? >> >> On Thu, Mar 12, 2015 at 5:38 PM, Romain Manni-Bucau >> <[email protected]> wrote: >> > Yes. Not released yet. >> > Le 12 mars 2015 21:45, "Jean-Louis Monteiro" <[email protected]> >> a >> > écrit : >> > >> >> Hi, >> >> >> >> I can recall a weird scanning issue but I thought Romain fixed it, but >> >> sounds like no. >> >> @Romain? >> >> >> >> JLouis >> >> >> >> >> >> -- >> >> Jean-Louis Monteiro >> >> http://twitter.com/jlouismonteiro >> >> http://www.tomitribe.com >> >> >> >> On Thu, Mar 12, 2015 at 9:39 PM, jieryn <[email protected]> wrote: >> >> >> >> > I have a fresh Apache TomEE 1.7.1 PLUS unpacked. My ROOT.war web >> >> > application has many @WebServlets in WEB-INF/lib/*jar files. If I >> >> > start the application they are automatically discovered. If I now >> >> > symlink the apache-tomee-plus-1.7.1 to be apache-tomee-wtf, and then >> >> > start up exactly the same way, these @WebServlets are not found. >> >> > >> >> > Bizarrely, other WEB-INF/lib/*jar files which contain via >> >> > web-fragment.xml things like servlet filters and other configuration >> >> > data (session, tracking, security constraints, etc) are picked up. >> >> > >> >> > The symlink does not span mount points or block devices. They are just >> >> > sitting in the same directory. There are no tricky issues with spaces >> >> > or unicode or other special characters in any paths. ... This really >> >> > is frustrating, why is TomEE not finding these @WebServlets? >> >> > >> >> > Thanks! >> >> > >> >> >>
