Wow, I am very sorry for the trouble I caused. BTW my filters work now differently (I updated my machine) so I just saw this thread now. Sorry!
see more inline. El sáb, 24-09-2005 a las 14:21 +1000, David Crossley escribió: > 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 Yes it is possible to revert certain files and directory only cd $FORREST_HOME svn up cd $FORREST_HOME/whiteboard/plugins/org.apache.forrest.plugin.output.viewHelper.xhtml svn up -r280939 cd ../org.apache.forrest.plugin.internal.view/ svn up -r280939 cd $FORREST_HOME/main ./build.sh clean ./build.sh cd $FORREST_HOME/etc ./views.sh Make sure you deleted all lib that you may have added meanwhile. I am very sorry that this changes makes your life harder. We are working hard to fix it. > > 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. Yeah, that is right, I prepared views for the core and we run into a bug in linkrewriter and jxpath. :( I am trying to debug that but it is not that easy. :( salu2 > -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 > > -- thorsten "Together we stand, divided we fall!" Hey you (Pink Floyd)
