I finally managed a workaround for issue FOR-675. The JXPath has been upgraded and tested with both the current "skins" and the new structurer (views v2) plugins.
Thorsten, does this mean that we can finally encourage devs to use the new whiteboard plugins, or is there another holdup? -David > Author: crossley > Date: Wed Oct 26 19:06:08 2005 > New Revision: 328770 > > URL: http://svn.apache.org/viewcvs?rev=328770&view=rev > Log: > Workaround to Issue FOR-675: > "upgrading to commons-jxpath-1.2.jar causes failures > with linkrewriter protocols site: etc." > This workaround removes the default namespace from site.xml > before the Cocoon input modules read it. > Upgraded from commons-jxpath-20030909 to commons-jxpath-1.2 > > Added: > forrest/trunk/lib/core/commons-jxpath-1.2.jar (with props) > forrest/trunk/lib/core/commons-jxpath-1.2.jar.license.txt > - copied, changed from r328762, > forrest/trunk/lib/core/commons-jxpath-20030909.jar.license.txt > Removed: > forrest/trunk/lib/core/commons-jxpath-20030909.jar > forrest/trunk/lib/core/commons-jxpath-20030909.jar.license.txt > Modified: > forrest/trunk/main/webapp/resources/stylesheets/site-to-book.xsl > forrest/trunk/main/webapp/sitemap.xmap [ snip ]
