jakarta-taglibs-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Glenn Nielsen <gl...@voyager.apg.more.net>
Subject Re: [PROPOSAL] Update Jakarta-Taglibs site to reflect reality
Date Wed, 03 Apr 2002 15:40:16 GMT
Shawn Bayern wrote:
> 
> Hi Glenn.
> 
> Looks like a great plan, and I agree wholeheartedly that it needs to be
> done.
> 
> There's one thing I might suggest, even though it's somewhat conservative:
> I was thinking it might be useful to wait until JSTL 1.0's final release
> (around the end of May) to do other 1.0 releases here, just so we'll know
> for sure how best to integrate with JSTL.  (For instance, adding or
> removing one JSTL tag might affect how we'd do a 1.0 release of another
> taglib here.)
> 
> Certainly, any planning up to that point would be useful.  But since we're
> less than two months away from final JSTL FCS, it might be easier for
> users if we hold off on early 1.0 releases (which might necessitate almost
> immediate 1.1 "synch" revs with JSTL 1.0.).
> 

JSTL compatability implies JSP1.2.  The existing taglibs need to be released
as 1.0 for those who use then in a JSP 1.1 container.  So these releases can
be done anytime, the sooner, the better.  Then we can go into maintenance mode
on them.

Then any existing taglibs which have features not available in JSTL, such
as the mailer, can either be branched, or create a new JSP1.2 STL compatible
version of the taglib, i.e. STLMailer.  I am not sure which is the best way to go.

If we branch the code I can just create a new nightly build script that checks
out the branchs and does a nightly build on the branch.  And the current one
which does a nightly build on the CVS HEAD.

> One more thought:  is it time, perhaps, to discontinue active enhancement
> of JSP 1.1 taglibs?  Maybe this is too aggressive, but a 1.0 release of a
> JSP 1.1 taglib might, at this point in time, be a wonderful opportunity to
> "freeze" its features and pick up active development on a JSP 1.2
> counterpart?  The list of categories would then become more like
> 
>     a. JSP 1.2 taglibs    (under active development)
>     b. JSP 1.1 taglibs    (frozen except for bug fixes)
>     c. Deprecated taglibs (frozen except for important bug fixes)
> 
> DBTags might go into category (B), while the XSL taglib would clearly be
> for (C).  I'm not sure if this marginalizes JSP 1.1 too much, but I
> figured I'd propose it.  It might give users clearer direction about our
> status.
> 

I agree.

> Personally, I'm happy to volunteer to help you do this, offering as much
> time as is necessary to get it done (including addressing bugs and other
> outstanding issues with the various taglibs).  However, JSTL is currently
> my first priority, so I don't want to commit to work on other taglibs
> until FCS of JSTL 1.0.  [ So, you see I have a selfish reason for
> proposing a more conservative schedule, too.  :-) ]   For what that's
> worth...
> 

Thanks

Glenn

> Shawn
> 
> On Tue, 2 Apr 2002, Glenn Nielsen wrote:
> 
> > With the release of JSP 1.2 last fall and the beta relase of the JSP
> > Standard Taglib (JSTL) the Jakarta-Taglibs site and taglibs could use
> > an update that reflects the current state of the taglibs.  And most
> > of the taglibs have never had an official release, or just a beta release.
> >
> > I have seen a number of questions regarding the release status of the
> > taglibs.
> >
> > I would like to propose the following changes and actions to get the
> > Jakarta-Taglibs site and taglibs up to date.
> >
> > 1. Work through and resolve any taglib bugs reported in bugzilla for
> > all taglibs.
> >
> > 2. Once all bugs are resolved, do an official 1.0 release of all taglibs.
> >
> > 3. Organize the list of taglibs into three categories.
> >
> >    a.  JSP 1.2 taglibs
> >    b.  JSP 1.1 taglibs
> >    c.  Deprecated taglibs (Deprecated taglibs will no longer be maintained)
> >
> > 4. Identify taglibs to deprecate, one that should be is XSL since it relies
> >    on Xalan 1.x and has a good replacement of either xtags or jstl.
> >    Another might be Foundation which was superceded by JSTL.
> >
> > 5. Identify those taglibs which can be replaced by the JSTL for those
> >    using a container that supports JSP 1.2.
> >
> > 6. Would it be beneficial to port some of the current taglibs such as mailer,
> >    scrape, and regexp to a JSP1.2 version which leverages the JSTL?
> >
> > Finally, I would like to call for volunteers to get the existing taglibs
> > into shape, i.e. resolve open bugs, etc. for release.  I can act as release
> > manager for all taglibs when they are ready.
> >
> > Regards,
> >
> > Glenn
> >
> > ----------------------------------------------------------------------
> > Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
> > MOREnet System Programming               |  * if iz ina coment.      |
> > Missouri Research and Education Network  |  */                       |
> > ----------------------------------------------------------------------
> >
> > --
> > To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>
> >
> 
> --
> To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>

-- 
----------------------------------------------------------------------
Glenn Nielsen             glenn@more.net | /* Spelin donut madder    |
MOREnet System Programming               |  * if iz ina coment.      |
Missouri Research and Education Network  |  */                       |
----------------------------------------------------------------------

--
To unsubscribe, e-mail:   <mailto:taglibs-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:taglibs-dev-help@jakarta.apache.org>


Mime
View raw message