[
https://issues.apache.org/jira/browse/JSPWIKI-796?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13728924#comment-13728924
]
Juan Pablo Santos RodrÃguez commented on JSPWIKI-796:
-----------------------------------------------------
I recall reading sometime ago (more than 3 moths ago), the discussion of moving
onto Tomcat 6.x -JSP2.1/Servlet 2.5-, maybe when we dropped the precompilation
tasks, although I haven't been able to find when or where. In fact, I think
that "discussion" would be too generous as it wasn't a big deal and was
something pretty straightforward then
OTOH, our $SVN/trunk/README file is currenty saying:
{code}
Pre-requirements
----------------
Okay, so you wanna Wiki? You'll need the following things:
REQUIRED:
* A JSP engine that supports Servlet API 2.4. We recommend Tomcat from
http://tomcat.apache.org/ for a really easy installation.
Tomcat 5.5.x or later is supported.
* Some previous administration experience... If you've ever installed
Apache or any other web server, you should be pretty well off.
* And of course, a server to run the JSP engine on.
* JDK 1.5+
OPTIONAL:
* JavaMail package from java.sun.com, if you want to use log4j mailing
capabilities. You'll also need the Java Activation Framework.
* RCS versioning system installed and available in your PATH if you
want to use RCS versioning. It is also possible (and on Windows, it
is even recommended) to use the VersioningFileProvider, which does
not require RCS.
{code}
where RCS support has been deprecated (JSPWIKI-758), we require JDK1.6+ and
somehow I was convinced we were on JSP 2.1 + Servlet 2.5 since 2.9 :-?
Also, http://jspwiki.apache.org/jspwiki/development/source_and_guide.html says
nothing about this, and IMO it should be the place to look for this kind of
information (note that we're currently unable to edit the site..)
Changes updating/upgrading requirements (i.e.: JDK, servlet+jsp, moving to
another kind of VCS, build tool,.. things like that) should be previously
discussed. I think that in this case it was done, although briefly (more or
less when dropping 5.5 precompilation tasks?), but I could be mistaken of
course, I don't remember when or where clearly.
Proposed course of action:
* lazy consensus on current trunk (JSP 2.1 / Servlet 2.5), to avoid reverting
commits, voting, applying them again
* until, let's say, next wednesday, hear pros&cons, wants/not wants on moving
onto JSP 2.1 + Servlet 2.5
* update README with whatever we decide
* update our "Building Source" page @ website with the same information, when
we're able to
* further changes on minimum requirements discussed at dev, as we've been
informally been doing
(I think that a formal vote isn't necessary, so let's keep the discussion on
this JIRA)
sound reasonable?
br,
juan pablo
> 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
