On Oct 27, 2008, at 1:20 PM October 27, Henri Yandell wrote:
Anyone going to be at ApacheCon?
Am pondering some effort to release the latest code in trunk.
I'll be there with bells on -- happy to re-live some old times hacking
on taglibs with you. :)
--
On Oct 25, 2007, at 11:28 PM October 25, Henri Yandell wrote:
"Think we should get rid of the 1.1.3 FAQ page or blow it away?".
Both say 'delete the page' to me; which is cool.
Oh, right. Don't ask me what I was thinking when I wrote that. :)
It's done.
Bjorn
--
On Oct 25, 2007, at 10:33 PM October 25, Henri Yandell wrote:
Done and done. When I merged the FAQ on the 1.1.3 page into the main
one I cleaned it up a bit so the wiki makes a nice table of contents
for us. Think we should get rid of the 1.1.3 FAQ page or blow it
away?
Both? Not sure wha
On Oct 25, 2007, at 7:36 PM October 25, Henri Yandell wrote:
I just realized there are two FAQs - we need to:
a) Merge the new FAQ on the 1.1.3 page into the main one and;
b) Rename the link on the main page to indicate that it is a JSTL FAQ
- there's nothing about any other taglib there afa
Hello the list,
I'm writing to suggest that the following be resolved -- it's got a
workaround and there's a FAQ entry written for it, so in my opinion
it's not impactful enough to worry about bothering with in a future
1.0.x release.
http://issues.apache.org/bugzilla/show_bug.cgi?id=298
Hello all,
Regarding the following:
http://issues.apache.org/bugzilla/show_bug.cgi?id=43393
I looked into the issue but wasn't able to reproduce it. Henri, can
you think of anything I might have missed in my attempt at reproing
it? If not, and we don't hear from the reporter, might be punt
On Sep 27, 2007, at 9:49 PM September 27, Bjorn Townsend wrote:
Makes sense. Might also be worth considering that this code is
probably already from an out of date Collections release -- it
might be worth comparing it to the current release to see how much
has changed.
I've crea
On Sep 27, 2007, at 9:37 PM September 27, Henri Yandell wrote:
Currently I'm avoiding the Collections refactor. Bugfixes win; though
the worry is that people might start depending on the code as it's
necessarily public.
Makes sense. Might also be worth considering that this code is
probabl
On Sep 26, 2007, at 10:02 PM September 26, Henri Yandell wrote:
Looks good - I'll look into committing it tomorrow night, unless
anyone sees a reason not to.
Thanks for looking at it. I'll be happy to help out with the
refactoring of the stuff from Collections.
Bjorn
---
On Sep 26, 2007, at 12:06 AM September 26, Henri Yandell wrote:
1.0.x as opposed to 1.1.x. Which raises the question, what else was
committed to 1.0.x that was not committed to 1.1.x (or to Commons EL).
After poking around the svn repository, it looks like this is the
only thing. The tags
I've gone ahead and created a patch for 1.1 and attached it to the
issue:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31789
Unit tests pass nicely.
Thanks,
Bjorn
On Sep 26, 2007, at 12:06 AM September 26, Henri Yandell wrote:
* Is there any interest in adopting this solution for
On Sep 26, 2007, at 12:06 AM September 26, Henri Yandell wrote:
Yikes. Glad they did, when I looked at doing it in the latest
Collections code, I seem to recall it feeling like a pain as there
were ties to more than just the one class. This is presumably an older
copy.
The commit logs impl
Hello all,
I'm working with a customer who is running into the bug described here:
http://issues.apache.org/bugzilla/show_bug.cgi?id=31789
As a result of which, I've been doing a lot of research into the
history of the problem as a lot of approaches have been suggested and
(possibly) discar
13 matches
Mail list logo