On 3/5/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
All software includes garbage that you don't want. Look at any library out
there. The beauty IMO is in the ease of implementation. We are currently
switching from JSP to JSF and as time goes by I think you will see more people
making the switch once they realize the simplicity of JSF. So now you have a
jar called -JSP, should it be JSF?
It may be all semantics but you really can't use tiles-jsp alone. So if each
is dependant on the other then why not have them combined? I can't really see
an argument that there would be a tiles-jsf, tiles-jsp, tiles-php, and
tiles-aspx. If I am irritating anyone let me know but I am trying to
contribute to what I believe is an excellent tool.
Freedom to release different versions at different times. If we
combine them, then we must wait until all are up to GA quality before
releasing the project as GA.
As David just said, we can offer a bundled "all" distribution, which
again can be released and graded without inhibiting the rest, but i
would not be happy about always having to drag the whole bunch around
together and waiting for tiles-jsp to be GA when i really only care
about tiles-core.
Scot
----- Original Message ----
From: Greg Reddin <[EMAIL PROTECTED]>
To: [email protected]
Sent: Monday, March 5, 2007 9:22:52 AM
Subject: Re: Current snapshot
On 3/5/07, Antonio Petrelli <[EMAIL PROTECTED]> wrote:
>
> About dependency maintenance, I think that it can be succesfully
> managed through the use of Maven at every level.
That's my thought as well. If we break them up it's trivial in Maven to
include everything we need. If we bundle them all together it's non-trivial
to try to exclude the stuff you don't want.
Greg
____________________________________________________________________________________
Now that's room service! Choose from over 150,000 hotels
in 45,000 destinations on Yahoo! Travel to find your fit.
http://farechase.yahoo.com/promo-generic-14795097
