Kevin wrote: > David Crossley wrote: > > Kevin wrote: > > > > > > Could you help with the svn command to revert back to a revision # > > > with working views and commons-jxpath-20030909.jar? > > > > Work backwards from today. Get the revision numbers from > > the Forrest SVN mailing list, e.g. > > http://www.mail-archive.com/svn%40forrest.apache.org/ > > Find a number, then subtract 1 from it > > e.g. to go to just before the most recent change to > > views stuff (r290290). > > > > svn update -r 290289 > > then test, if still broken then go further ... > > > > svn update -r 290163 > > ... > > Thanks for that it was an iterative process though I > arrived at r280939 after jumping blocks of revisions. > Can I go forward from r280939 eg: svn update -r 290946 > to fine tune.
Yes, you can update to any revision number or directly back to head. See 'svn help update' and svnbook.red-bean.com > I do appreciate the hard work the devs are doing here > and sorry for raising FOR-678 as *major* with error: Thanks. No need to be sorry. It actually should be *blocker*. > X [0] linkmap.html BROKEN: > org.apache.commons.jxpath.JXPathContext.setNamespaceContextPointer > (Lorg/apache/commons/jxpath/Pointer;)V > > It doesn't mean anything to me though I understand your > in heavy refactoring mode and your on top of it. It is just that some committers are starting to exercise the use of jxpath in the development of views, and so exposing some new issues. -David > Downloading commons-jxpath-1.2.jar and looking at the > docs without being a java or cocoon person I can see > xpath xslt in java code! Maybe I have an idea of what > is happening or not :( > > Kevin >
