Hi Pierre,
Pierre Delisle wrote:
Apologies for the long silence. As noted by Felipe, Sun has been
focusing a lot of its energies on GlassFish lately and we've been
lacking the resources to stay active at jakarta taglibs.
[And I know I could use my spare time to work on apache stuff,
At least you have your office hours to work on Glassfish :-)
but the 4 kids have been asking a lot of attention as well lately...]
Next year I'm also joining the club of 'the webtier guys with a lot of
kids', formed at JavaOne 2004, as my wife is expecting twins...
I've raised the issue with management so we can clarify the situation
regarding the standard tag library and on our involvement within
jakarta-taglibs. I'll update this list whenever decisions are made.
Ok, thanks. Please CC the PMC list as well (I'm CC'ing this message,
although it might bounce because I'm not subscribed there with this
address).
Rahul, feel free to apply your patch. I would recommend running
the TCK as well (Felipe can fill you in).
Regarding the TCK, I have 2 questions:
1.Should we get a generic JSTL TCK for ASF? I mean, I have my personal
TCK as an individual member an Rahul could get his as well, but the
process takes time and that time would be spent over and over again for
each new committer willing to work on the TCK.
2.I haven't been able to automatize the use of the TCK by an Ant build.
From what I read and talked with some guys, that would be possible,
although how is not well documented. So, here comes my second question:
would it worth the effort to have the TCK in our builds if we are not
hosting future versions of the JSTL? I mean, we don't even say we are a
certified implementation of the technology right now so if we are not
going to be the base for the next versions, we better leave the TCK
support as is.
[]s,
-- Felipe
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
