You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by "Brian K. Wallace" <br...@transmorphix.com> on 2006/04/27 03:15:10 UTC
Building....
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUBseaCoPKRow/gARAh+aAJ91lkiFPixFLCyp7BTE6pgT/20k6QCdFosB
BJdxa/iMlYqwSJhZmSYkIm0=
=Ih6R
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Move to Maven [was re: Building...]
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Yep. Got that, too. :-)
Massimo Lusetti wrote:
> On 4/28/06, Brian K. Wallace <br...@transmorphix.com> wrote:
>
>> I've done some Maven (1) projects so I don't think it'll be such a shock
>> getting it broken up the way we want it. I'm just looking at how Forrest
>> does its job and cringe.
>>
>> I'll work on it and then post back my results - make sure I'm on the
>> same page as everyone else.
>
> Maybe you all already know but there's a free book from Mergere about
> Maven 2.0 which could help in the process.
>
> --
> Massimo
> http://meridio.blogspot.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUhI7aCoPKRow/gARAkPDAKDD9UsYl0+W2FjjeAeAtzPlPwlgugCgkGoA
XR9hfwWAVTGZFdHzpXOZQ5A=
=CpNw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Move to Maven [was re: Building...]
Posted by Massimo Lusetti <ml...@gmail.com>.
On 4/28/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> I've done some Maven (1) projects so I don't think it'll be such a shock
> getting it broken up the way we want it. I'm just looking at how Forrest
> does its job and cringe.
>
> I'll work on it and then post back my results - make sure I'm on the
> same page as everyone else.
Maybe you all already know but there's a free book from Mergere about
Maven 2.0 which could help in the process.
--
Massimo
http://meridio.blogspot.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Move to Maven [was re: Building...]
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've done some Maven (1) projects so I don't think it'll be such a shock
getting it broken up the way we want it. I'm just looking at how Forrest
does its job and cringe.
I'll work on it and then post back my results - make sure I'm on the
same page as everyone else.
Howard Lewis Ship wrote:
> I've been doing some work on Maven2 for HiveMind.
>
> I have an XSL stylesheet to convert from Forrest XML document format
> to Maven XML document format (though its not perfect).
>
> Part of "Mavenizing" is to convert from one project that builds
> everything into a number of sub-projects. So a Maven module for
> framework, for contrib, for annotations, for portlet support, for each
> of the examples.
>
> I'm still learning all the best practices for Maven 2.
>
> The Tapestry @ JavaForge stuff is also a good reference for layout and
> implementation ... but again, there are tricks I've just learned about
> Maven2 that don't show up there.
>
> Still, the essense of Maven is that all builds are flat. That is, you
> don't create a deep project hierarchy, you keep it flat with each of
> the sub-projects as simple peers of each other, even when there are
> interdependencies (i.e., tapestry-contrib.jar depends on
> tapestry.jar). You can define modules that bulid tapestry.jar and
> tapestry-contrib.jar, and Maven will build them in the correct order.
>
> On 4/27/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> As this is a "one for, one against" (as no one else has spoken up), I'll
> just put it up on my area on people - no problem doing that. I'll also
> look at mavenizing the builds, although I'm somewhat concerned that it
> won't be a walk in the park getting all the component references in
> there. This won't fix anyone wanting to build an old release, but at
> least having a snapshot somewhere on apache is better than saying "can't
> do it anymore unless you already have it".
>
> Here's hoping I can leverage the work Howard's done in Mavenizing 5.x,
> and the component reference building work done by Norbert [This won't
> handle 'examples', but hopefully it'll be available for use]
>
> Are there any objections to a move to Maven 2 at this time (schedule for
> inclusion in 3.1/4.1 - not immediately) for the 3.x and 4.x threads? If
> not, I'll start with branching and go from there.
>
> Howard: Are there any 'gotchas' that you ran across that I should be
> aware of? Or was your 5.x work so completely different that it isn't
> comparable?
>
> FYI - My plan will end up with:
> tapestry-site/
> tapestry-4/
> tapestry-3/
> with tapestry-site/ being the 'parent' (if I understand maven
> terminology correctly). The goal being to be able to build 3 and site
> for a 3 release, or 4 and site for a 4 release thereby keeping the two
> 'code' branches separate at build/release time.
>
> Question about 'site': Assuming there are no objections and I go ahead
> with this, should I fit the site to its current look? Is the design of
> http://people.apache.org/~bwallace/tapsite acceptable? Are there
> alternatives other than these two options? (If I'm going to do it, I'd
> love to do it the way it's going to end up instead of treading back over
> to convert to a new design for TLP)
>
> As usual, thoughts/comments/questions welcome...
>
> Brian
>
> Brian K. Wallace wrote:
>>>> I completely agree that we shouldn't depend on a snapshot version - the
>>>> problem is... We already do. That's the problem. If anyone tries to
>>>> build what we have now, they must use the snapshot version. The problem
>>>> with the "latest" forrest is either a) the 'latest' is still a snapshot,
>>>> but now uses forrestbot and a different cocoon producing errors
>>>> througout the build or b) 0.7 which dies due to cocoon versions.
>>>>
>>>> I'm not thinking about "building by us" (since I was apparently the only
>>>> one having issues building and they're now resolved), but for anyone
>>>> else wanting to get into the fray it would be impossible to find a
>>>> download off the forrest site that would work to build the current sites.
>>>>
>>>> Andreas Andreou wrote:
>>>>>> 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...
>>>>>>
>>>>>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUWy5aCoPKRow/gARAv3BAKDTzHEHkLxAg01cuIegNp/SstqMegCfQFKO
ZJZAwl5DYWih77M6zA0L90M=
=sPTm
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Move to Maven [was re: Building...]
Posted by Howard Lewis Ship <hl...@gmail.com>.
I've been doing some work on Maven2 for HiveMind.
I have an XSL stylesheet to convert from Forrest XML document format
to Maven XML document format (though its not perfect).
Part of "Mavenizing" is to convert from one project that builds
everything into a number of sub-projects. So a Maven module for
framework, for contrib, for annotations, for portlet support, for each
of the examples.
I'm still learning all the best practices for Maven 2.
The Tapestry @ JavaForge stuff is also a good reference for layout and
implementation ... but again, there are tricks I've just learned about
Maven2 that don't show up there.
Still, the essense of Maven is that all builds are flat. That is, you
don't create a deep project hierarchy, you keep it flat with each of
the sub-projects as simple peers of each other, even when there are
interdependencies (i.e., tapestry-contrib.jar depends on
tapestry.jar). You can define modules that bulid tapestry.jar and
tapestry-contrib.jar, and Maven will build them in the correct order.
On 4/27/06, Brian K. Wallace <br...@transmorphix.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> As this is a "one for, one against" (as no one else has spoken up), I'll
> just put it up on my area on people - no problem doing that. I'll also
> look at mavenizing the builds, although I'm somewhat concerned that it
> won't be a walk in the park getting all the component references in
> there. This won't fix anyone wanting to build an old release, but at
> least having a snapshot somewhere on apache is better than saying "can't
> do it anymore unless you already have it".
>
> Here's hoping I can leverage the work Howard's done in Mavenizing 5.x,
> and the component reference building work done by Norbert [This won't
> handle 'examples', but hopefully it'll be available for use]
>
> Are there any objections to a move to Maven 2 at this time (schedule for
> inclusion in 3.1/4.1 - not immediately) for the 3.x and 4.x threads? If
> not, I'll start with branching and go from there.
>
> Howard: Are there any 'gotchas' that you ran across that I should be
> aware of? Or was your 5.x work so completely different that it isn't
> comparable?
>
> FYI - My plan will end up with:
> tapestry-site/
> tapestry-4/
> tapestry-3/
> with tapestry-site/ being the 'parent' (if I understand maven
> terminology correctly). The goal being to be able to build 3 and site
> for a 3 release, or 4 and site for a 4 release thereby keeping the two
> 'code' branches separate at build/release time.
>
> Question about 'site': Assuming there are no objections and I go ahead
> with this, should I fit the site to its current look? Is the design of
> http://people.apache.org/~bwallace/tapsite acceptable? Are there
> alternatives other than these two options? (If I'm going to do it, I'd
> love to do it the way it's going to end up instead of treading back over
> to convert to a new design for TLP)
>
> As usual, thoughts/comments/questions welcome...
>
> Brian
>
> Brian K. Wallace wrote:
> > I completely agree that we shouldn't depend on a snapshot version - the
> > problem is... We already do. That's the problem. If anyone tries to
> > build what we have now, they must use the snapshot version. The problem
> > with the "latest" forrest is either a) the 'latest' is still a snapshot,
> > but now uses forrestbot and a different cocoon producing errors
> > througout the build or b) 0.7 which dies due to cocoon versions.
> >
> > I'm not thinking about "building by us" (since I was apparently the only
> > one having issues building and they're now resolved), but for anyone
> > else wanting to get into the fray it would be impossible to find a
> > download off the forrest site that would work to build the current sites.
> >
> > Andreas Andreou wrote:
> >>> 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...
> >>>
> >>>
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEUNfPaCoPKRow/gARAr0ZAJ4+Oo9lk+1GmsKCYQPf8mznol6jUgCcCAFg
> 8CcbxdxYhJ2S1v4F+F0OvIc=
> =BfYq
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator and PMC Chair, Apache Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Move to Maven [was re: Building...]
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As this is a "one for, one against" (as no one else has spoken up), I'll
just put it up on my area on people - no problem doing that. I'll also
look at mavenizing the builds, although I'm somewhat concerned that it
won't be a walk in the park getting all the component references in
there. This won't fix anyone wanting to build an old release, but at
least having a snapshot somewhere on apache is better than saying "can't
do it anymore unless you already have it".
Here's hoping I can leverage the work Howard's done in Mavenizing 5.x,
and the component reference building work done by Norbert [This won't
handle 'examples', but hopefully it'll be available for use]
Are there any objections to a move to Maven 2 at this time (schedule for
inclusion in 3.1/4.1 - not immediately) for the 3.x and 4.x threads? If
not, I'll start with branching and go from there.
Howard: Are there any 'gotchas' that you ran across that I should be
aware of? Or was your 5.x work so completely different that it isn't
comparable?
FYI - My plan will end up with:
tapestry-site/
tapestry-4/
tapestry-3/
with tapestry-site/ being the 'parent' (if I understand maven
terminology correctly). The goal being to be able to build 3 and site
for a 3 release, or 4 and site for a 4 release thereby keeping the two
'code' branches separate at build/release time.
Question about 'site': Assuming there are no objections and I go ahead
with this, should I fit the site to its current look? Is the design of
http://people.apache.org/~bwallace/tapsite acceptable? Are there
alternatives other than these two options? (If I'm going to do it, I'd
love to do it the way it's going to end up instead of treading back over
to convert to a new design for TLP)
As usual, thoughts/comments/questions welcome...
Brian
Brian K. Wallace wrote:
> I completely agree that we shouldn't depend on a snapshot version - the
> problem is... We already do. That's the problem. If anyone tries to
> build what we have now, they must use the snapshot version. The problem
> with the "latest" forrest is either a) the 'latest' is still a snapshot,
> but now uses forrestbot and a different cocoon producing errors
> througout the build or b) 0.7 which dies due to cocoon versions.
>
> I'm not thinking about "building by us" (since I was apparently the only
> one having issues building and they're now resolved), but for anyone
> else wanting to get into the fray it would be impossible to find a
> download off the forrest site that would work to build the current sites.
>
> Andreas Andreou wrote:
>>> 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...
>>>
>>>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUNfPaCoPKRow/gARAr0ZAJ4+Oo9lk+1GmsKCYQPf8mznol6jUgCcCAFg
8CcbxdxYhJ2S1v4F+F0OvIc=
=BfYq
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Building....
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I completely agree that we shouldn't depend on a snapshot version - the
problem is... We already do. That's the problem. If anyone tries to
build what we have now, they must use the snapshot version. The problem
with the "latest" forrest is either a) the 'latest' is still a snapshot,
but now uses forrestbot and a different cocoon producing errors
througout the build or b) 0.7 which dies due to cocoon versions.
I'm not thinking about "building by us" (since I was apparently the only
one having issues building and they're now resolved), but for anyone
else wanting to get into the fray it would be impossible to find a
download off the forrest site that would work to build the current sites.
Andreas Andreou wrote:
> 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...
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUL1haCoPKRow/gARAtCwAJ96N4mwMlXIaGJpCLEp/PdV1CsyXQCfas6B
32oMUm/5aodWQ/i6/2JwYXw=
=YFIr
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Building....
Posted by Andreas Andreou <an...@di.uoa.gr>.
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...
>
> andyhot@di.uoa.gr 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" <br...@transmorphix.com>:
>
> >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: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
> >>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Building....
Posted by "Brian K. Wallace" <br...@transmorphix.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
? 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...
andyhot@di.uoa.gr 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" <br...@transmorphix.com>:
>
> 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: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>>
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (MingW32)
iD8DBQFEUCHqaCoPKRow/gARAqvHAJ9uJguSs+i795jfVJmHCzpxIFompwCgmZ8b
Anl/agYD2fnsJ89H7thXaUI=
=aVO2
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Building....
Posted by an...@di.uoa.gr.
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" <br...@transmorphix.com>:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.5 (MingW32)
>
> iD8DBQFEUBseaCoPKRow/gARAh+aAJ91lkiFPixFLCyp7BTE6pgT/20k6QCdFosB
> BJdxa/iMlYqwSJhZmSYkIm0=
> =Ih6R
> -----END PGP SIGNATURE-----
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org