Thanks. As Henri said, real life is occupying me at the moment.
The outstanding work on 1.2 is really just the release process (with a bit of
cleanup for Maven 3.0) and the website. I don't have time to finish that but
would be able to run the TCK against a candidate.
46052 still needs to be
On Jun 4, 2013, at 11:10 AM, Garry S Ditzler gditz...@csc.com wrote:
According to your website, the latest stable version of Taglibs is 1.1.2.
However, 1.1.2 appears to have been released back in October 2004. Is
Taglibs 1.1.2 still actively supported for things like security issues?
The Apache Tomcat team announces the immediate availability of Apache Standard
Apache Standard Taglib is an open source software implementation of the JSP
Standard Tag Library (JSTL) technology.
This release supports JSTL version 1.2 along with numerous bug-fixes and
> On Nov 27, 2017, at 12:07 AM, Matthew Broadhead
> In TomEE 7.0.3 everything is fine at startup. But if a webapp is reloaded I
> java.lang.ClassCastException: org.apache.xml.dtm.ref.DTMManagerDefault cannot
> be cast to
> On Nov 27, 2017, at 7:38 AM, Romain Manni-Bucau <rmannibu...@apache.org>
> 2017-11-27 16:31 GMT+01:00 Jeremy Boynes <jboy...@apache.org>:
>> On Nov 27, 2017, at 12:07 AM, Matthew Broadhead
>> <matthew.broadh...@nbmlaw.co.uk> wrote:
On Nov 26, 2017, at 6:32 AM, Matthew Broadhead
> I am currently evaluating whether the Xalan dependency can be dropped from
> taglibs and replaced with javax.xml.*.
> The reason for this is a conflict which occurs when I have Apache Fop as a
> On Nov 26, 2017, at 2:17 PM, Matthew Broadhead
> So to run the tests I could reverse the changes of the commit and then update
> to javax.xml.* and run tests?
> I am still struggling a bit to understand exactly what is happening wrt
> On Nov 30, 2017, at 3:14 AM, Matthew Broadhead
> has anything been decided? if i try to redeploy a context in production all
> my xslt processors blow up. there should be a solution that fits all?
Taglibs (both Apache and Glassfish) has always