Before you do that, I'd make sure that antlr isn't in the server
repo. That way you will know that there isn't another library using
it. Antlr is very popular after all.
-dain
On Feb 6, 2007, at 5:54 AM, Matt Hogstrom wrote:
Since we're not using the CMP generator of TranQL in 2.x I think we
can drop the Antlr reference as well. Any objections?
On Feb 5, 2007, at 12:29 PM, Dain Sundstrom wrote:
Tranql uses antlr, but there may be something else that does
(maybe spring).
-dain
On Feb 4, 2007, at 3:13 AM, Gianny Damour wrote:
Hi Jarek,
I think the Spring filter is a leftover of the time when the
Jetty module was used to import Spring to configure WADI.
I do not know why antlr is there. As it is not directly imported
by Jetty6 poms, I think that we can also drop it.
Thanks,
Gianny
On 02/02/2007, at 3:07 PM, Jarek Gawor wrote:
Hi,
I have a question about the following entry in the
configs/jett6-deployer/src/plan/plan.xml:
<hidden-classes>
<filter>antlr.</filter>
<filter>org.springframework.</filter>
</hidden-classes>
Is that still needed/necessary? tomcat6-deployer's plan.xml does
not
have such entry. So is this jetty specific? I believe this is
causing
problems for me with a WS client code that uses Spring API to
configure itself (a WS client gets an automatic dependency on CXF
which then has a dependency on the Spring API).
Can someone please explain?
Thanks,
Jarek
