You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can see everyone standing around going should I shouldn't I, someone has to
say it.
When are we applying the 1.8 specification?
I guess this has to be addressed at some point.
Do we have any roadmap or are you aware of any major obstacles perhaps?
+1 on the 1.5 deprecation and move to 1.7 \o/
Latest tomcat 6.0.x stands on 6.0.37 or if we take on Servlet 3.0 jsp 2.2 then
the 7.0.x release would be 7.0.41. But that is merely the most obvious of the
dependencies and lots has changed over the last 3 years. Do we even want to
hold on to some of these dependencies like hibernate, king of the crop back
then but now theres JCA and several new kids on the block. It even seems odd
not to find lucene in the mix which has became common place on these stacks, am
I wrong?
@Mark I picked up from your discussions that you are weary of breaking anything
but by the look of things that might be just what we need. I can assure you
things will break if we replace the stack but isn't that the best thing to do
at this junction. What says yous?
LOL Yes they say when it rains it pours =) it's been quiet foc so long and I
for one am relieved to see some action since I am new to the party. Colour me
impressed Mark you've managed to keep tabs on things all this time. Kudos!
Well done!
Original issue reported on code.google.com by [email protected] on 4 Jul 2013 at 12:23
The text was updated successfully, but these errors were encountered:
There currently is no roadmap and no plans for 1.8 compatibility at this point.
Funding for Variman was terminated a couple of years back and community support
is minimal these days. There are some patches that come in and occasionally
users will hire me for support or to make changes. But, nothing as major as 1.8
is on the horizon.
However, this remains open source and a community project. I encourage users to
take the ball and run should they so desire.
As for breaking changes ... I'm usually against that since that causes grief
for existing users. So far I've been able to incrementally add changes or do
them in such a way that they won't break existing sites. I also encourage that
approach until such time as it is impossible to continue down that path.
Original comment by jazzklein on 6 Jul 2013 at 5:53
Original issue reported on code.google.com by
[email protected]
on 4 Jul 2013 at 12:23The text was updated successfully, but these errors were encountered: