[
https://issues.apache.org/jira/browse/JSPWIKI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728874#comment-13728874
]
Glen Mazza commented on JSPWIKI-796:
------------------------------------
@ Harry, I think the decision to drop support for Tomcat 5 should not be made
by us but by the Tomcat team, which they explicitly did last year
(http://tomcat.apache.org/tomcat-55-eol.html). Note Dirk wants support not
only for Tomcat 5.5 but also Tomcat 5.0, which the Tomcat team last patched in
October 2007 (http://svn.apache.org/viewvc/tomcat/archive/tc5.0.x/tags/). Even
the build.xml we were Mavenizing was using Tomcat 5.5 for precompilation. At
this time, I think the burden is on Dirk for him to first veto the change on
the Dev mailing list and provide valid reasons--"oh, we didn't have a vote on
that JSTL version upgrade"--alone is not a legitimate reason (where was our
vote on Dirk's change to wro4j?), as we operate on lazy consensus. After his
veto, then we can have a vote.
@ Dirk, that JSTL upgrade was made 3-4 months ago and nobody, including
yourself, complained about it. Part of the problem was that you weren't active
on the team at the time and bothering to look at the commits. Those who were
didn't mind the change. You can't go sleep on the project for six months and
then demand votes on everything that occurred you didn't like while you were
inactive. Use your veto pen instead.
As for "Unless I missed some updates to that" -- the JSPWiki site is read-only
(read the top of the page), it's frozen, that's why there's no updates to it.
What you missed were the commits that you failed to veto several months ago.
While some people like Harry turned out to still have write access to it
(something I didn't know at the time), other team members like myself don't, so
it cannot be considered a definitive site. As write access to that site is not
automatic based on team membership but a function of Janne's decisions (it's
fully within his rights to say "no" and I earlier made clear my desire to
update it...), it can't be definitive for JSPWiki.
> UserPreferences is broken
> -------------------------
>
> Key: JSPWIKI-796
> URL: https://issues.apache.org/jira/browse/JSPWIKI-796
> Project: JSPWiki
> Issue Type: Bug
> Components: Default template
> Affects Versions: 2.10
> Reporter: brushed
> Assignee: Glen Mazza
>
> (detected on v2.10.0-svn-22)
> The new JSTL version, upgraded to version 1.2 since the MAVEN update, is
> giving problems in resolving certain EL expressions.
> EG, the UserPreference page is throwing an error when evaluating a forEach
> loop.
> {noformat}
> java.lang.NoClassDefFoundError: javax/el/ValueExpression
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2475)
> at java.lang.Class.privateGetPublicMethods(Class.java:2595)
> at java.lang.Class.getMethods(Class.java:1437)
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
