Thanks, Simone, I will go for the old artisanal mode. ;-) (and see where I land).
On Thu, 2010-03-04 at 14:48 +0100, Simone Tripodi wrote: > Hi Jos :) > unfortunately for the sax module you should perform an extra-step > invoking JavaCC by hand, then in Eclipse add the generated-sources dir > as a source dir; this is what the JavaCC plugin for maven does for us > :P > Let me know if you need help!!! > Ciao ;) > Simo > > http://people.apache.org/~simonetripodi/ > > > > On Thu, Mar 4, 2010 at 1:59 PM, Jos Snellings <jos.snelli...@pandora.be> > wrote: > > Hi Simone! > > > > I am sorry, I do not use maven for the build. > > I imported the sources as Eclipse projects, and from there I > > interconnected them via dependencies. I just import the very external > > stuff from the maven repository. > > Ay, so you mean this is where my 'nice private build' ends? :-( > > > > Ciao, > > Jos > > > > On Thu, 2010-03-04 at 12:34 +0100, Simone Tripodi wrote: > >> Hi Jos, > >> these classes are not committed because they're generated from JavaCC, > >> the JavaCC plugin should be invoked during the 'generate-source' maven > >> phase... > >> Doesn't it work for you? > >> Best, > >> Simo > >> > >> http://people.apache.org/~simonetripodi/ > >> > >> > >> > >> On Thu, Mar 4, 2010 at 11:04 AM, Jos Snellings <jos.snelli...@pandora.be> > >> wrote: > >> > Hi! > >> > > >> > In the full checkout of the cocoon-3 SVN repository I am missing: > >> > org.apache.cocoon.sax.xpointer.XPointerFrameworkParser; > >> > org.apache.cocoon.sax.xpointer.ParseException; > >> > > >> > This prevents XIncludeTransformer from compiling. Any idea why? > >> > > >> > Jos > >> > > >> > > >> > On Thu, 2010-03-04 at 07:36 +0100, Reinhard Pötz wrote: > >> >> Jos Snellings wrote: > >> >> > Hi, > >> >> > > >> >> > Is the hereunder described issue with XML serializers known? > >> >> > > >> >> > A sitemap having several xml serialization patterns: > >> >> > > >> >> > <map:pipeline> > >> >> > <map:match pattern="showterm.xml"> > >> >> > <map:generate type="term"/> > >> >> > <map:serialize type="xml"/> > >> >> > </map:match> > >> >> > <map:match pattern="hierarchies"> > >> >> > <map:generate type="topterms"/> > >> >> > <map:serialize type="xml" /> > >> >> > </map:match> > >> >> > > >> >> > ... > >> >> > > >> >> > This pipeline is observed to have an 'eternal cache': > >> >> > whichever pattern is matched first gives the correct answer. > >> >> > All subsequent requests, whatever the URL, whatever the get-parameters > >> >> > return the contents of the cache. > >> >> > > >> >> > In order to get fresh results you need to destroy the caching stuff > >> >> > under work/... first. > >> >> > > >> >> > Is this known? I may as well get rid of it by checking out the very > >> >> > last > >> >> > cocoon-3 version! Just asking. > >> >> > >> >> Could you create a JIRA issue please and attach a failing sample please? > >> >> Also add the version of C3 (release or SVN revision) that you use. > >> >> > >> >> Thanks! > >> >> > >> > > >> > > >> > > >> > --------------------------------------------------------------------- > >> > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > >> > For additional commands, e-mail: users-h...@cocoon.apache.org > >> > > >> > > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > >> For additional commands, e-mail: users-h...@cocoon.apache.org > >> > >> > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > > For additional commands, e-mail: users-h...@cocoon.apache.org > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org > For additional commands, e-mail: users-h...@cocoon.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@cocoon.apache.org For additional commands, e-mail: users-h...@cocoon.apache.org
