New in JSPWiki 2.11.0.M2 - Released on 08/03/2019#

Apache JSPWiki 2.11.0.M2 is the second release towards 2.11.0.

This release features, among other things:

  • Haddock Dark appereance, enabled by default
    • if you want to keep the Light appereance by default, set jspwiki.defaultprefs.template.appearance to false on your jspwiki[-custom].properties file
  • Fixes related to Haddock being the default template as of 2.11.0.M1
    • Fixes for Reader view (JSPWIKI-1090Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png), Diff view (JSPWIKI-1091Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png) and WYSIWYG editor, which were incorrectly rendered
    • Fallback to default template if the requested template folder is not found - JSPWIKI-1088Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
      • this allows to 2.10 installations having set to haddock the jspwiki.templateDir property to keep that value, as opposed to 2.11.0.M1 behaviour
  • Fixed buggy header width in Fixed Page Layout - JSPWIKI-1074Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
  • Upgraded bundled dependencies - JSPWIKI-1092Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • flexmark to 0.40.16
    • gson to 2.8.5
    • junit to 5.4.0
    • lucene to 7.7.0
    • nekohtml to 1.9.22
    • stripes to 1.7.0-async (needed to test JSPWIKI-1088)
    • tomcat to 8.5.38
  • Devs only
    • classes on org.apache.wiki.util package have been moved to their own maven module, org.apache.jspwiki:jspwiki-util

New in JSPWiki 2.11.0.M1 - Released on 29/01/2019#

Apache JSPWiki 2.11.0.M1 is the first release towards 2.11.0.

This release features, among other things:

  • Haddock as new default template - JSPWIKI-1083Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
  • Default locale can now be set server-side through the jspwiki.preferences.default-localeContent unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png property on your jspwiki[-custom].properties file - JSPWIKI-1085Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
  • Fix for JSPWIKI-932Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png: Failed to start managers. java.util.ConcurrentModificationException
  • Third-party plugin jars are loaded as much as possible, instead of the all-or-nothing approach on 2.10 - JSPWIKI-1080Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
  • New requirements - JSPWIKI-1076Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • Java 8 needed to run JSPWiki
    • Servlet 3.1 / JSP 2.3 compliant JEE server (i.e., Tomcat 8.5 and onwards)
  • Upgraded bundled dependencies - JSPWIKI-1087Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • commons-fileupload to 1.4
    • ehcache to 2.10.6
    • flexmark to 0.40.12
    • junit to 5.3.2
    • lucene to 7.6.0
      • 2.10.X users: when upgrading, Lucene index must be rebuilt in order to get the search going; to do so you'll have to delete the jspwiki.workDir/lucene directory
    • tomcat to 8.5.37
  • Devs only:
    • New JSPWiki jar maven coordinates: org.apache.jspwiki:jspwiki-main - JSPWIKI-1081Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • At least JDK 8 and Maven 3.5.0 needed to build JSPWiki - JSPWIKI-1076Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • JUnit 5 is now used for testing - JSPWIKI-1078Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • Functional tests now use Selenide instead of Selenium - JSPWIKI-1086Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png
    • Backwards API incompatible changes: https://jspwiki.apache.org/japicmp/2.11.0.M1/Content unavailable! (broken link)https://jspwiki-vm1.apache.org/images/out.png

What does that M# mean anyway?#

M# releases are as production-ready as any other JSPWiki release, so you should not be concerned about its stability.

Please look at the VersioningProposal page to know how this label is used on Apache JSPWiki releases.


NewIn