-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Well, I figured out my XSL issue - I had the saxon.jar I needed for the
3.X build in my ant\lib (where it needs to be for 3.X) and it naturally
led to a completely different error in 4.X. *sigh*

That let me get farther - but I can't finish. I still don't have access
to the committer's svn to get the clover license, so... I figure I've
made it through the quirks part - but can't get past the 403: Forbidden
part (on SVN).

That said: Although I believe it should all just be built, I did go
through manually with a 'find' doing a grep for 3.0.3 (tapestry/3.0.3,
actually) and replaced them one by one (to make sure and get only what I
wanted) with 3.0.4. That gets it live now - if you want to build and
redploy, that's cool. I went through the site and verified 3.0.4 appears
in all the sections, on all the pages with the nav.

Any idea who handles https://svn.apache.org/repos/private/committers/
access?

Brian K. Wallace wrote:
> Oh, I've got no problems working through it - just figured if you had
> seen the issue before it might be faster to ask than not. Yeah, I've got
> the latest Forrest (which builds to 0.8-dev). Will see if I can't figure
> something out.
> 
> Thanks
> Jesse Kuhnert wrote:
>>> I've not had any "serious" problems with the current 4.0 branch + forrest,
>>> but I've always downloaded the "latest nightly snapshot" version as that is
>>> what I found referenced in the wiki documentation I found.
>>>
>>> Try that and see if you still have problems. ( I can always just build it
>>> tomorrow morning if it's annoying, but if you're just trying to learn all
>>> the quircks then the latest nightly should probably do it.)
>>>
>>> On 4/16/06, Brian K. Wallace <[EMAIL PROTECTED]> wrote:
>>> Not sure if here or hivemind would be best to ask this, but since a) it
>>> has to have been handled for Tapestry for the current site to be done
>>> and b) a lot of Tapestry devs are Hivemind devs to a certain extent so:
>>>
>>> I'm getting the following error when I attempt "ant site" on the 4.Xbranch:
>>>
>>>      [echo] *** Building HiveDoc ...
>>>      [echo]
>>>      [xslt] Processing C:\Temp\jakarta-tapestry\tapestry
>>> \target\registry.xml to C:\Temp\jakarta-tapestry\target\
>>> docs\tapestry\hivedocs\index.html
>>>      [xslt] Loading stylesheet
>>> C:\hivemind-1.1.1\hivebuild\hivedoc-xsl\hivemind.
>>> xsl
>>>      [xslt] Writing master index to C:\Temp\jakarta-tape
>>> stry\target\docs\tapestry\hivedocs
>>>      [xslt] Writing module hivemind.lib
>>>      [xslt]
>>> file:/C:/hivemind-1.1.1/hivebuild/hivedoc-xsl/hivemind.xsl:201: Fata
>>> l Error! Unknown extension element
>>>      [xslt] Failed to process C:\Temp\jakarta-tapestry\t
>>> apestry\target\registry.xml
>>>
>>> The offending line is the redirect:write below:
>>>   <xsl:template match="module">
>>>     <xsl:message>Writing module <xsl:value-of select="@id"/></xsl:message>
>>>     <redirect:write file="{$base.dir}/module/[EMAIL PROTECTED]">
>>>
>>> I have 1.1.1 - but a big question for me is the forrest I have. Yes,
>>> it's 0.8-dev, but that's a floating rev. Not sure if this is a Hivemind
>>> problem that's been addressed, or a Forrest change that negatively
>>> impacts the Tapestry build. (and I have cleaned both the temp dir, and
>>> re-built)
>>>
>>> Anyone with a thought here or there?
>>>
>>> Brian
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>>>>
> 
>>> --
>>> Jesse Kuhnert
>>> Tacos/Tapestry, team member/developer
> 
>>> Open source based consulting work centered around
>>> dojo/tapestry/tacos/hivemind.  http://opennotion.com
> 
> 

- ---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]




-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)

iD8DBQFEQyjUaCoPKRow/gARArWUAKC7CbshgeX/C7K9wFoNpY/p46mrvQCg2zNr
MCIXN6MD2U8aacvcicZ1Mb8=
=fAlG
-----END PGP SIGNATURE-----

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to