Richard,
thanks for your patch. I removed the dependence of JBossXACML on Apache Xalan. I have
tested AS trunk to use JBossXACML 2.0.5.CR1 and it is fine.
I have not updated the AS workspace though.
Regards,
Anil
On 02/08/2010 08:57 AM, Richard Opalka wrote:
Not so urgent Brian. I'm just asking/analyzing ;)
This issue is currently scheduled for M3, see JBAS-2073.
According to my latest analysis, we can't remove xalan
from AS distro, but we should remove it from endorsed directory,
see:
http://community.jboss.org/message/524324#524784
Rio
On 02/08/2010 03:43 PM, Brian Stansberry wrote:
> What's the urgency of this? This is definitely not something I want to
> see changed on Thursday; it should happen and be tested before that, at
> latest your Wed in time for the hudson testsuite run that normally
> happens at 5AM EST. And if I'm interpreting some of these threads
> correctly, the WS changes that allow this are not in AS trunk yet. The
> component cutoff for M2 was a week ago. It's too late for a WS change
> unless there is some critical problem.
>
> On 02/08/2010 04:12 AM, Dimitris Andreadis wrote:
>
>
>> If you have removed xalan usage from your project (WS) then someone needs to run
tattletale
>> in AS to uncover all usages, to make sure we don't break something.
>>
>> Richard Opalka wrote:
>>
>>
>>> -------- Original Message --------
>>> Subject: Removing Xalan from AS distribution
>>> Date: Mon, 08 Feb 2010 09:18:22 +0100
>>> From: Richard Opalka<ropalka(a)redhat.com>
>>> To: jboss-dev-all(a)redhat.com
>>>
>>>
>>>
>>> Hi AS folks,
>>>
>>> could you comment on
>>>
>>>
http://community.jboss.org/message/524324#524324
>>>
>>> please? If there will be no complains I do plan to remove xalan from
>>> AS distro in M2 (code freeze this thursday)
>>>
>>> Rio
>>>
>>> --
>>>
>>> Richard Opalka
>>> ropalka(a)redhat.com
>>> JBoss, by Red Hat