You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by Pierre Delisle <Pi...@Sun.COM> on 2004/02/17 07:48:44 UTC
New Apache License, Version 2.0
Committers,
Per http://www.apache.org/dev/apply-license.html,
all ASF software distributions must be converted to the new license
(Apache License, Version 2.0) by March 1, 2004.
While there is a conversion program available to help with this task
(committers/relicense/relicense.py), it did not handle the preservation
of copyright dates, and is written in python (which I'm not familiar with
enough to hack).
I've therefore written a small conversion program in Java that
we can use to handle the conversion in jakarta-taglibs.
The program is named ReplaceLicense.java and has been saved in
the "committers" module, under the "relicense" directory
(along with the python program).
The description of the program is included below.
I've ran a few tests, and it seems fine. I'd appreciate if at least
one more person would also give it a try to make sure it performs
as planned. Once proper behavior is confirmed, we could then go ahead
and run the conversion on all of jakarta-taglibs.
Thanks,
-- Pierre
/*
* This program is used to replace
* the Apache License version 1.1 with the new
* Apache License version 2.0.
*
* See:
* http://www.apache.org/dev/apply-license.html
* http://www.apache.org/licenses
*
* Program can process a specific file, or recursively process
* all the files within a specific directory.
*
* Orginally written to handle license conversion in
* jakarta-taglibs (Pierre Delisle). Should also work with other projects.
* Please hack according to own needs.
*
* Usage: java ReplaceLicense [options] path
*
* where
* path: path to directory or file
* options:
* -n: test mode (no output saved)
* -r: recursively process directories
* By default, directories are ignored.
* -s: Replacement output is saved in the same file
* By default, output is saved in a new file with extension "_ALV20" added.
*
* The program preserves copyright dates, and updates them to 2004
* if necessary in the following way, where first match is applied:
* 2004 --> no modification
* -2003 --> 2003 replaced with 2004
* 2003 --> 2003 replaced with 2003-2004
* --> add ,2004
*
* Configuration:
* EXCLUDED_DIRS
* Array of directory names to be excluded
* EXCLUDED_SUFFIXES
* Array of file suffixes to be excluded
* EXCLUDED_PREFIXES
* Array of file prefixes to be excluded
*/
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Martin Cooper <ma...@apache.org>.
On Sun, 29 Feb 2004, Felipe Leme wrote:
> On Sun, 2004-02-29 at 04:53, Martin Cooper wrote:
> > I've converted the license in the Java sources of many of the taglibs, but
>
> Good work!!
>
> > there are still several that are unconverted (mainly because I'm not
> > in a position to build those at the moment, and I don't want to check
> > in files that I can't build).
>
> I understand the filling - I'd like to change a file on XSL a couple of
> days ago, but couldn't build that taglib (as it is a deprecated one, I
> gave up).
>
> > many other files that need the ALv2 license applied, such as the docs and
> > XML files.
>
> That's a good timing to fix/update these docs. Besides the license, we
> also have that inconsistent TLD naming issue (see bug 26508 -
> http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26508). Besides that,
> I'm improving the build.xml/common.xml process
>
> > Still, this will get us on the right track.
>
> Agreed.
>
> > I'm keeping a list of what
> > state each taglib is in, with respect to the new license, so if you make
> > license related changes, please let me know, so that I can update my list.
>
> Better yet, I think we should create a page in the site with the overall
> status of the tags, including:
>
> - current version
> - next version
> - status (deprecated, preparing for next, unable to build, converting
> licenses, licenses converted, stable, etc...)
> - current maintainer (name of the committer, vacant, abandoned, etc...)
> - pending bugs for next version (number of the bugs or none if stable)
> - other info (JSP version, date last release, date planned for next
> release, link for bugzilla bugs, etc...)
Yah, I was thinking about creating a web page, but I was too lazy at the
time. ;-) Also, I haven't played with updating the Taglibs site yet, so
I'm not sure what I would be letting myself in for...
>
>
> In fact, this is a good opportunity to release new versions for each
> taglib - once we finish the new license transition on each one and
> pending bugs (for instance, I fixed a couple of dbtags, random and
> scrape bugs over the week, and was going to send a vote message about
> releasing new versions).
For taglibs that have changes and / or bug fixes, yes, that makes sense.
There are undoubtedly some taglibs, though, that haven't changed, and I
don't think we have any need to re-release those.
--
Martin Cooper
>
>
> Felipe
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Felipe Leme <ja...@felipeal.net>.
On Tue, 2004-03-02 at 09:10, Glenn Nielsen wrote:
> It is great to see all the renewed activity in taglibs Thanks to
> Pierre, Felipe, Martin, and others.
That's a beginning - but we're still short compared to the number of
taglibs.
> It will be nice to see some new releases of existing taglibs.
Agreed. Once I finish some more bugs and read all the HOWTOs, I will
propose new releases for some.
> For any of you contemplating being a release manager I wrote up
> some documentation on how to do this at:
>
> http://jakarta.apache.org/taglibs/addtaglib.html
Interesting, I didn't know that document (I found the HOWTO_RELEASE on
CVS a couple of days ago, but this link is more complete).
Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Martin Cooper <ma...@apache.org>.
On Tue, 2 Mar 2004, Glenn Nielsen wrote:
> On Sun, Feb 29, 2004 at 12:02:01PM -0300, Felipe Leme wrote:
> <snip>
> > In fact, this is a good opportunity to release new versions for each
> > taglib - once we finish the new license transition on each one and
> > pending bugs (for instance, I fixed a couple of dbtags, random and
> > scrape bugs over the week, and was going to send a vote message about
> > releasing new versions).
>
> It is great to see all the renewed activity in taglibs Thanks to
> Pierre, Felipe, Martin, and others.
Just scratching my itch... ;-)
>
> It will be nice to see some new releases of existing taglibs.
>
> For any of you contemplating being a release manager I wrote up
> some documentation on how to do this at:
>
> http://jakarta.apache.org/taglibs/addtaglib.html
Very nice. I've been doing the RM thing for some time now, for Struts and
a few Jakarta Commons components, so I've got the basic idea down pat, but
there are clearly some Taglibs peculiarities, so this is great.
>
> This may need updating, its been a while since I looked at it.
>
> Things to add would be verifying that the release uses the new
> Apache 2.0 license. Another thing to add would be generation of
> an MD5 checksum for the release archives. (Some people prefer
> just checking the md5 checksum rather than verifying a PGP
> signature).
Yah, I've been generating both digests and signatures for Struts and
Commons for a while now. The only oddity I've found is that the MD5 files
generated on minotaur seem to need editing to conform to the norm of
what's in such a file.
--
Martin Cooper
>
> 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: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Glenn Nielsen <gl...@mail.more.net>.
On Sun, Feb 29, 2004 at 12:02:01PM -0300, Felipe Leme wrote:
<snip>
> In fact, this is a good opportunity to release new versions for each
> taglib - once we finish the new license transition on each one and
> pending bugs (for instance, I fixed a couple of dbtags, random and
> scrape bugs over the week, and was going to send a vote message about
> releasing new versions).
It is great to see all the renewed activity in taglibs Thanks to
Pierre, Felipe, Martin, and others.
It will be nice to see some new releases of existing taglibs.
For any of you contemplating being a release manager I wrote up
some documentation on how to do this at:
http://jakarta.apache.org/taglibs/addtaglib.html
This may need updating, its been a while since I looked at it.
Things to add would be verifying that the release uses the new
Apache 2.0 license. Another thing to add would be generation of
an MD5 checksum for the release archives. (Some people prefer
just checking the md5 checksum rather than verifying a PGP
signature).
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: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Felipe Leme <ja...@felipeal.net>.
On Sun, 2004-02-29 at 04:53, Martin Cooper wrote:
> I've converted the license in the Java sources of many of the taglibs, but
Good work!!
> there are still several that are unconverted (mainly because I'm not
> in a position to build those at the moment, and I don't want to check
> in files that I can't build).
I understand the filling - I'd like to change a file on XSL a couple of
days ago, but couldn't build that taglib (as it is a deprecated one, I
gave up).
> many other files that need the ALv2 license applied, such as the docs and
> XML files.
That's a good timing to fix/update these docs. Besides the license, we
also have that inconsistent TLD naming issue (see bug 26508 -
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26508). Besides that,
I'm improving the build.xml/common.xml process
> Still, this will get us on the right track.
Agreed.
> I'm keeping a list of what
> state each taglib is in, with respect to the new license, so if you make
> license related changes, please let me know, so that I can update my list.
Better yet, I think we should create a page in the site with the overall
status of the tags, including:
- current version
- next version
- status (deprecated, preparing for next, unable to build, converting
licenses, licenses converted, stable, etc...)
- current maintainer (name of the committer, vacant, abandoned, etc...)
- pending bugs for next version (number of the bugs or none if stable)
- other info (JSP version, date last release, date planned for next
release, link for bugzilla bugs, etc...)
In fact, this is a good opportunity to release new versions for each
taglib - once we finish the new license transition on each one and
pending bugs (for instance, I fixed a couple of dbtags, random and
scrape bugs over the week, and was going to send a vote message about
releasing new versions).
Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Martin Cooper <ma...@apache.org>.
I've converted the license in the Java sources of many of the taglibs, but
there are still several that are unconverted (mainly because I'm not in a
position to build those at the moment, and I don't want to check in files
that I can't build).
In addition, since I've only converted Java source files, there are still
many other files that need the ALv2 license applied, such as the docs and
XML files.
Still, this will get us on the right track. I'm keeping a list of what
state each taglib is in, with respect to the new license, so if you make
license related changes, please let me know, so that I can update my list.
--
Martin Cooper
On Tue, 17 Feb 2004, Pierre Delisle wrote:
> Martin Cooper wrote:
> >
> >>-----Original Message-----
> >>From: Pierre Delisle [mailto:Pierre.Delisle@Sun.COM]
> >>Sent: Monday, February 16, 2004 10:49 PM
> >>To: taglibs-dev@jakarta.apache.org
> >>Subject: New Apache License, Version 2.0
> >>
> >>
> >>Committers,
> >>
> >>Per http://www.apache.org/dev/apply-license.html,
> >>all ASF software distributions must be converted to the new license
> >>(Apache License, Version 2.0) by March 1, 2004.
> >
> >
> > It's worth noting that it's only the distributions released after March 1st
> > that need to have been converted. In other words, while it wouldn't be a bad
> > idea to update the licences on all of the Taglibs code by March 1st, what's
> > actually required is just that any releases after that date have the 2.0
> > license applied.
>
> Agree, but as you say, I don't think it would be a bad idea
> to do a clean sweep so we dont't have to worry about it in
> the future when modifying files.
>
> >
> >
> >>While there is a conversion program available to help with this task
> >>(committers/relicense/relicense.py), it did not handle the preservation
> >>of copyright dates, and is written in python (which I'm not familiar with
> >>enough to hack).
> >
> >
> > Actually, the Python script has been updated so that it does preserve the
> > copyright years. Unfortunately, it seems that the comment claiming that it
> > does not was not updated when that change was made.
>
> I should probably have checked first on the alias. Oh well, got me
> to thinker with the new java.util.regexp...
>
> >
> > Someone else (I forget who) has also written a Perl script to do the same
> > thing, although I don't believe that's been checked in yet.
> >
> > So, now that we have three choices of how to update the license, we have no
> > excuse not to do so. :-)
>
> Indeed...
>
> -- Pierre
>
> >
> > --
> > Martin Cooper
> >
> >
> >
> >>I've therefore written a small conversion program in Java that
> >>we can use to handle the conversion in jakarta-taglibs.
> >>The program is named ReplaceLicense.java and has been saved in
> >>the "committers" module, under the "relicense" directory
> >>(along with the python program).
> >>
> >>The description of the program is included below.
> >>
> >>I've ran a few tests, and it seems fine. I'd appreciate if at least
> >>one more person would also give it a try to make sure it performs
> >>as planned. Once proper behavior is confirmed, we could then go ahead
> >>and run the conversion on all of jakarta-taglibs.
> >>
> >>Thanks,
> >>
> >> -- Pierre
> >>
> >>
> >>/*
> >> * This program is used to replace
> >> * the Apache License version 1.1 with the new
> >> * Apache License version 2.0.
> >> *
> >> * See:
> >> * http://www.apache.org/dev/apply-license.html
> >> * http://www.apache.org/licenses
> >> *
> >> * Program can process a specific file, or recursively process
> >> * all the files within a specific directory.
> >> *
> >> * Orginally written to handle license conversion in
> >> * jakarta-taglibs (Pierre Delisle). Should also work with other projects.
> >> * Please hack according to own needs.
> >> *
> >> * Usage: java ReplaceLicense [options] path
> >> *
> >> * where
> >> * path: path to directory or file
> >> * options:
> >> * -n: test mode (no output saved)
> >> * -r: recursively process directories
> >> * By default, directories are ignored.
> >> * -s: Replacement output is saved in the same file
> >> * By default, output is saved in a new file with
> >>extension "_ALV20" added.
> >> *
> >> * The program preserves copyright dates, and updates them to 2004
> >> * if necessary in the following way, where first match is applied:
> >> * 2004 --> no modification
> >> * -2003 --> 2003 replaced with 2004
> >> * 2003 --> 2003 replaced with 2003-2004
> >> * --> add ,2004
> >> *
> >> * Configuration:
> >> * EXCLUDED_DIRS
> >> * Array of directory names to be excluded
> >> * EXCLUDED_SUFFIXES
> >> * Array of file suffixes to be excluded
> >> * EXCLUDED_PREFIXES
> >> * Array of file prefixes to be excluded
> >> */
> >>
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> >>For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
> >>
> >>
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> > For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
> >
> >
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
Re: New Apache License, Version 2.0
Posted by Pierre Delisle <Pi...@Sun.COM>.
Martin Cooper wrote:
>
>>-----Original Message-----
>>From: Pierre Delisle [mailto:Pierre.Delisle@Sun.COM]
>>Sent: Monday, February 16, 2004 10:49 PM
>>To: taglibs-dev@jakarta.apache.org
>>Subject: New Apache License, Version 2.0
>>
>>
>>Committers,
>>
>>Per http://www.apache.org/dev/apply-license.html,
>>all ASF software distributions must be converted to the new license
>>(Apache License, Version 2.0) by March 1, 2004.
>
>
> It's worth noting that it's only the distributions released after March 1st
> that need to have been converted. In other words, while it wouldn't be a bad
> idea to update the licences on all of the Taglibs code by March 1st, what's
> actually required is just that any releases after that date have the 2.0
> license applied.
Agree, but as you say, I don't think it would be a bad idea
to do a clean sweep so we dont't have to worry about it in
the future when modifying files.
>
>
>>While there is a conversion program available to help with this task
>>(committers/relicense/relicense.py), it did not handle the preservation
>>of copyright dates, and is written in python (which I'm not familiar with
>>enough to hack).
>
>
> Actually, the Python script has been updated so that it does preserve the
> copyright years. Unfortunately, it seems that the comment claiming that it
> does not was not updated when that change was made.
I should probably have checked first on the alias. Oh well, got me
to thinker with the new java.util.regexp...
>
> Someone else (I forget who) has also written a Perl script to do the same
> thing, although I don't believe that's been checked in yet.
>
> So, now that we have three choices of how to update the license, we have no
> excuse not to do so. :-)
Indeed...
-- Pierre
>
> --
> Martin Cooper
>
>
>
>>I've therefore written a small conversion program in Java that
>>we can use to handle the conversion in jakarta-taglibs.
>>The program is named ReplaceLicense.java and has been saved in
>>the "committers" module, under the "relicense" directory
>>(along with the python program).
>>
>>The description of the program is included below.
>>
>>I've ran a few tests, and it seems fine. I'd appreciate if at least
>>one more person would also give it a try to make sure it performs
>>as planned. Once proper behavior is confirmed, we could then go ahead
>>and run the conversion on all of jakarta-taglibs.
>>
>>Thanks,
>>
>> -- Pierre
>>
>>
>>/*
>> * This program is used to replace
>> * the Apache License version 1.1 with the new
>> * Apache License version 2.0.
>> *
>> * See:
>> * http://www.apache.org/dev/apply-license.html
>> * http://www.apache.org/licenses
>> *
>> * Program can process a specific file, or recursively process
>> * all the files within a specific directory.
>> *
>> * Orginally written to handle license conversion in
>> * jakarta-taglibs (Pierre Delisle). Should also work with other projects.
>> * Please hack according to own needs.
>> *
>> * Usage: java ReplaceLicense [options] path
>> *
>> * where
>> * path: path to directory or file
>> * options:
>> * -n: test mode (no output saved)
>> * -r: recursively process directories
>> * By default, directories are ignored.
>> * -s: Replacement output is saved in the same file
>> * By default, output is saved in a new file with
>>extension "_ALV20" added.
>> *
>> * The program preserves copyright dates, and updates them to 2004
>> * if necessary in the following way, where first match is applied:
>> * 2004 --> no modification
>> * -2003 --> 2003 replaced with 2004
>> * 2003 --> 2003 replaced with 2003-2004
>> * --> add ,2004
>> *
>> * Configuration:
>> * EXCLUDED_DIRS
>> * Array of directory names to be excluded
>> * EXCLUDED_SUFFIXES
>> * Array of file suffixes to be excluded
>> * EXCLUDED_PREFIXES
>> * Array of file prefixes to be excluded
>> */
>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
>>For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>>
>>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
RE: New Apache License, Version 2.0
Posted by Martin Cooper <ma...@apache.org>.
> -----Original Message-----
> From: Pierre Delisle [mailto:Pierre.Delisle@Sun.COM]
> Sent: Monday, February 16, 2004 10:49 PM
> To: taglibs-dev@jakarta.apache.org
> Subject: New Apache License, Version 2.0
>
>
> Committers,
>
> Per http://www.apache.org/dev/apply-license.html,
> all ASF software distributions must be converted to the new license
> (Apache License, Version 2.0) by March 1, 2004.
It's worth noting that it's only the distributions released after March 1st
that need to have been converted. In other words, while it wouldn't be a bad
idea to update the licences on all of the Taglibs code by March 1st, what's
actually required is just that any releases after that date have the 2.0
license applied.
>
> While there is a conversion program available to help with this task
> (committers/relicense/relicense.py), it did not handle the preservation
> of copyright dates, and is written in python (which I'm not familiar with
> enough to hack).
Actually, the Python script has been updated so that it does preserve the
copyright years. Unfortunately, it seems that the comment claiming that it
does not was not updated when that change was made.
Someone else (I forget who) has also written a Perl script to do the same
thing, although I don't believe that's been checked in yet.
So, now that we have three choices of how to update the license, we have no
excuse not to do so. :-)
--
Martin Cooper
>
> I've therefore written a small conversion program in Java that
> we can use to handle the conversion in jakarta-taglibs.
> The program is named ReplaceLicense.java and has been saved in
> the "committers" module, under the "relicense" directory
> (along with the python program).
>
> The description of the program is included below.
>
> I've ran a few tests, and it seems fine. I'd appreciate if at least
> one more person would also give it a try to make sure it performs
> as planned. Once proper behavior is confirmed, we could then go ahead
> and run the conversion on all of jakarta-taglibs.
>
> Thanks,
>
> -- Pierre
>
>
> /*
> * This program is used to replace
> * the Apache License version 1.1 with the new
> * Apache License version 2.0.
> *
> * See:
> * http://www.apache.org/dev/apply-license.html
> * http://www.apache.org/licenses
> *
> * Program can process a specific file, or recursively process
> * all the files within a specific directory.
> *
> * Orginally written to handle license conversion in
> * jakarta-taglibs (Pierre Delisle). Should also work with other projects.
> * Please hack according to own needs.
> *
> * Usage: java ReplaceLicense [options] path
> *
> * where
> * path: path to directory or file
> * options:
> * -n: test mode (no output saved)
> * -r: recursively process directories
> * By default, directories are ignored.
> * -s: Replacement output is saved in the same file
> * By default, output is saved in a new file with
> extension "_ALV20" added.
> *
> * The program preserves copyright dates, and updates them to 2004
> * if necessary in the following way, where first match is applied:
> * 2004 --> no modification
> * -2003 --> 2003 replaced with 2004
> * 2003 --> 2003 replaced with 2003-2004
> * --> add ,2004
> *
> * Configuration:
> * EXCLUDED_DIRS
> * Array of directory names to be excluded
> * EXCLUDED_SUFFIXES
> * Array of file suffixes to be excluded
> * EXCLUDED_PREFIXES
> * Array of file prefixes to be excluded
> */
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: taglibs-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: taglibs-dev-help@jakarta.apache.org