How about adding the zip in another server then...?
http://people.apache.org/~andyhot/support/

It's just that i don't like such artifacts within version control +
we shouldn't depend on a snapshot version.
What exactly were the issues with latest forrest? Are they difficult to fix?
Perhaps it's an opportunity to switch to maven then...


Brian K. Wallace wrote:

> ? Add forrest to the website? Ummm... kinda of defeats the
> 'reproducible' part. (Ideally, the site should be able to be rebuilt
> with an svn up if anything happens - that wouldn't work since we need to
> build it, but then we'd lose the snapshot that works) What is the
> downside to just zipping it up and putting it in SVN since it's a
> dependency to build? (and you can't get this version anymore)
>
> as for t.a.o - I think it's just time...
>
> [EMAIL PROTECTED] wrote:
>
> >hmmm... actually i wouldn't like this in the svn...
>
> >Why not add it on the website, perhaps in
> >jakarta.apache.org/tapestry/support
>
> >BTW, any reason why we haven't moved the site to
> >tapestry.apache.org yet?
>
> >>From "Brian K. Wallace" <[EMAIL PROTECTED]>:
>
> >Okay. I know you guys are probably sick of messages from me saying "I
> >can't build - Help!", so that's not what this is...
>
> >FINALLY - I have no idea how or why - but FINALLY I have my system set
> >up to build 4.x - Complete with changes.html, todo.html and no
> >favicon.ico. *whew* No clue yet if the same setup will work for 3.x, but
> >I know how to reconfigure for that if it doesn't.
>
> >I'm cleaning every temp area I have, running an ant clean and going to
> >do an "ant install site" - and if that works, I'd like to check in to
> >SVN a zip of the forrest I've got that will build everything. I would
> >like to create a component up at the top level that would have to be
> >checked out separately - a "support" (or pick a better name) component.
> >I don't want this kind of thing messing with the SVN tree of
> >trunk/branches/tags inside with the code since once you've got it, it's
> >there - no need to check it out every time. Any objections to that?
>
> >(may seem like a waste, but this makes it so it's reproducible)
>
> >Brian
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
> >>
>

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



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

Reply via email to