You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by Martin van den Bemt <ml...@mvdb.net> on 2003/01/17 22:29:45 UTC
[jelly][betwixt]
Hi everyone,
I was thinking about removing the betwixt taglib from jelly and putting
it in betwixt itself. (although with the current seperation going on, it
shouldn't give a lot of problems when it remains in jelly).
Any ideas?
Mvgr,
Martin
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Martin van den Bemt <ml...@mvdb.net>.
Note: (wtf everyone I have to reply to doesn't have the reply to set the
mailinglist, really anoying)
With the seperation of builds that is currently ongoing I meant to say
that it is possible to release a new betwixt tag library when betwixt
does a release or a change, seperately from the jelly core (not talking
about building stuff, that's another issue, on which I agree with you
anyway), which wasn't possible before.
Despite the tags can have seperate release cycles from the jelly core, I
was suggesting/asking if a move for the betwixt stuff to betwixt itself
, would be more appropiate.
Mvgr,
Martin
On Fri, 2003-01-17 at 22:41, Morgan Delagrange wrote:
> I think the Betwixt tags might be better as a separate
> build, although that build could be under the Jelly or
> Betwixt tree.
>
> Here's the rule of thumb IMO. If an application
> cannot be executed without Jelly (e.g. Maven, Latka),
> then the application should host the tags in its main
> build. Contrarily if the Jelly tags is simply an
> alternative syntax for a library (e.g. Betwixt,
> HttpClient), then those tags should have a separate
> build rather than pulling all the Jelly dependencies
> into the main build. All IMO.
>
> - Morgan
>
> --- Martin van den Bemt <ml...@mvdb.net> wrote:
> > Hi everyone,
> >
> > I was thinking about removing the betwixt taglib
> > from jelly and putting
> > it in betwixt itself. (although with the current
> > seperation going on, it
> > shouldn't give a lot of problems when it remains in
> > jelly).
> >
> > Any ideas?
> >
> > Mvgr,
> > Martin
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
>
>
> =====
> Morgan Delagrange
> http://jakarta.apache.org/taglibs
> http://jakarta.apache.org/commons
> http://axion.tigris.org
> http://jakarta.apache.org/watchdog
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Morgan Delagrange <md...@yahoo.com>.
+1 from me, if that's what betwixt wants. :)
- Morgan
--- Martin van den Bemt <ml...@mvdb.net> wrote:
> Is this +1 on the move of the jelly tags for betwixt
> to betwxit itself ?
> (the thing I was investigating..)
>
> Mvgr,
> Martin
>
> On Sat, 2003-01-18 at 06:52, James Strachan wrote:
> > +1
> >
> > From: "Morgan Delagrange" <md...@yahoo.com>
> > > I think the Betwixt tags might be better as a
> separate
> > > build, although that build could be under the
> Jelly or
> > > Betwixt tree.
> > >
> > > Here's the rule of thumb IMO. If an application
> > > cannot be executed without Jelly (e.g. Maven,
> Latka),
> > > then the application should host the tags in its
> main
> > > build. Contrarily if the Jelly tags is simply
> an
> > > alternative syntax for a library (e.g. Betwixt,
> > > HttpClient), then those tags should have a
> separate
> > > build rather than pulling all the Jelly
> dependencies
> > > into the main build. All IMO.
> >
> > Good rule.
> >
> > James
> > -------
> > http://radio.weblogs.com/0112098/
> > __________________________________________________
> > Do You Yahoo!?
> > Everything you'll ever need on one web page
> > from News and Sport to Email and Music Charts
> > http://uk.my.yahoo.com
> >
> > --
> > To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> <ma...@jakarta.apache.org>
> >
> >
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Martin van den Bemt <ml...@mvdb.net>.
Is this +1 on the move of the jelly tags for betwixt to betwxit itself ?
(the thing I was investigating..)
Mvgr,
Martin
On Sat, 2003-01-18 at 06:52, James Strachan wrote:
> +1
>
> From: "Morgan Delagrange" <md...@yahoo.com>
> > I think the Betwixt tags might be better as a separate
> > build, although that build could be under the Jelly or
> > Betwixt tree.
> >
> > Here's the rule of thumb IMO. If an application
> > cannot be executed without Jelly (e.g. Maven, Latka),
> > then the application should host the tags in its main
> > build. Contrarily if the Jelly tags is simply an
> > alternative syntax for a library (e.g. Betwixt,
> > HttpClient), then those tags should have a separate
> > build rather than pulling all the Jelly dependencies
> > into the main build. All IMO.
>
> Good rule.
>
> James
> -------
> http://radio.weblogs.com/0112098/
> __________________________________________________
> Do You Yahoo!?
> Everything you'll ever need on one web page
> from News and Sport to Email and Music Charts
> http://uk.my.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by James Strachan <ja...@yahoo.co.uk>.
+1
From: "Morgan Delagrange" <md...@yahoo.com>
> I think the Betwixt tags might be better as a separate
> build, although that build could be under the Jelly or
> Betwixt tree.
>
> Here's the rule of thumb IMO. If an application
> cannot be executed without Jelly (e.g. Maven, Latka),
> then the application should host the tags in its main
> build. Contrarily if the Jelly tags is simply an
> alternative syntax for a library (e.g. Betwixt,
> HttpClient), then those tags should have a separate
> build rather than pulling all the Jelly dependencies
> into the main build. All IMO.
Good rule.
James
-------
http://radio.weblogs.com/0112098/
__________________________________________________
Do You Yahoo!?
Everything you'll ever need on one web page
from News and Sport to Email and Music Charts
http://uk.my.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Martin van den Bemt <ml...@mvdb.net>.
That's the thing I was talking about :)
Mvgr,
Martin
On Fri, 2003-01-17 at 22:52, Rodney Waldhoff wrote:
> I like Morgan's "opinion" on this.
>
> A third option would be a separate build/jar within betwixt itself.
> Distinguishing between the a separate build in betwixt and a separate
> build in jelly might be function of how "central" the tags are to jelly.
> My personal preference would be to keep the jelly tags next to the
> libraries themselves, although in the near term it might be just as well
> to leave them within the jelly tree, at least until jelly stablizes (read
> "releases"?) a bit more.
>
> On Fri, 17 Jan 2003, Morgan Delagrange wrote:
>
> > I think the Betwixt tags might be better as a separate
> > build, although that build could be under the Jelly or
> > Betwixt tree.
> >
> > Here's the rule of thumb IMO. If an application
> > cannot be executed without Jelly (e.g. Maven, Latka),
> > then the application should host the tags in its main
> > build. Contrarily if the Jelly tags is simply an
> > alternative syntax for a library (e.g. Betwixt,
> > HttpClient), then those tags should have a separate
> > build rather than pulling all the Jelly dependencies
> > into the main build. All IMO.
> >
> > - Morgan
> >
> > --- Martin van den Bemt <ml...@mvdb.net> wrote:
> > > Hi everyone,
> > >
> > > I was thinking about removing the betwixt taglib
> > > from jelly and putting
> > > it in betwixt itself. (although with the current
> > > seperation going on, it
> > > shouldn't give a lot of problems when it remains in
> > > jelly).
> > >
> > > Any ideas?
> > >
> > > Mvgr,
> > > Martin
> > >
> > >
> > >
> > >
> > >
> > > --
> > > To unsubscribe, e-mail:
> > > <ma...@jakarta.apache.org>
> > > For additional commands, e-mail:
> > > <ma...@jakarta.apache.org>
> > >
> >
> >
> > =====
> > Morgan Delagrange
> > http://jakarta.apache.org/taglibs
> > http://jakarta.apache.org/commons
> > http://axion.tigris.org
> > http://jakarta.apache.org/watchdog
> >
> > __________________________________________________
> > Do you Yahoo!?
> > Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> > http://mailplus.yahoo.com
> >
> > --
> > To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Rodney Waldhoff <rw...@apache.org>.
I like Morgan's "opinion" on this.
A third option would be a separate build/jar within betwixt itself.
Distinguishing between the a separate build in betwixt and a separate
build in jelly might be function of how "central" the tags are to jelly.
My personal preference would be to keep the jelly tags next to the
libraries themselves, although in the near term it might be just as well
to leave them within the jelly tree, at least until jelly stablizes (read
"releases"?) a bit more.
On Fri, 17 Jan 2003, Morgan Delagrange wrote:
> I think the Betwixt tags might be better as a separate
> build, although that build could be under the Jelly or
> Betwixt tree.
>
> Here's the rule of thumb IMO. If an application
> cannot be executed without Jelly (e.g. Maven, Latka),
> then the application should host the tags in its main
> build. Contrarily if the Jelly tags is simply an
> alternative syntax for a library (e.g. Betwixt,
> HttpClient), then those tags should have a separate
> build rather than pulling all the Jelly dependencies
> into the main build. All IMO.
>
> - Morgan
>
> --- Martin van den Bemt <ml...@mvdb.net> wrote:
> > Hi everyone,
> >
> > I was thinking about removing the betwixt taglib
> > from jelly and putting
> > it in betwixt itself. (although with the current
> > seperation going on, it
> > shouldn't give a lot of problems when it remains in
> > jelly).
> >
> > Any ideas?
> >
> > Mvgr,
> > Martin
> >
> >
> >
> >
> >
> > --
> > To unsubscribe, e-mail:
> > <ma...@jakarta.apache.org>
> > For additional commands, e-mail:
> > <ma...@jakarta.apache.org>
> >
>
>
> =====
> Morgan Delagrange
> http://jakarta.apache.org/taglibs
> http://jakarta.apache.org/commons
> http://axion.tigris.org
> http://jakarta.apache.org/watchdog
>
> __________________________________________________
> Do you Yahoo!?
> Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
> http://mailplus.yahoo.com
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: [jelly][betwixt]
Posted by Morgan Delagrange <md...@yahoo.com>.
I think the Betwixt tags might be better as a separate
build, although that build could be under the Jelly or
Betwixt tree.
Here's the rule of thumb IMO. If an application
cannot be executed without Jelly (e.g. Maven, Latka),
then the application should host the tags in its main
build. Contrarily if the Jelly tags is simply an
alternative syntax for a library (e.g. Betwixt,
HttpClient), then those tags should have a separate
build rather than pulling all the Jelly dependencies
into the main build. All IMO.
- Morgan
--- Martin van den Bemt <ml...@mvdb.net> wrote:
> Hi everyone,
>
> I was thinking about removing the betwixt taglib
> from jelly and putting
> it in betwixt itself. (although with the current
> seperation going on, it
> shouldn't give a lot of problems when it remains in
> jelly).
>
> Any ideas?
>
> Mvgr,
> Martin
>
>
>
>
>
> --
> To unsubscribe, e-mail:
> <ma...@jakarta.apache.org>
> For additional commands, e-mail:
> <ma...@jakarta.apache.org>
>
=====
Morgan Delagrange
http://jakarta.apache.org/taglibs
http://jakarta.apache.org/commons
http://axion.tigris.org
http://jakarta.apache.org/watchdog
__________________________________________________
Do you Yahoo!?
Yahoo! Mail Plus - Powerful. Affordable. Sign up now.
http://mailplus.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>