I was almost certain that temporarily putting these seemingly benign
classes in "nodeps" to avoid Log4J dependency and still preserve
deprecated API was a bad idea. Just didn't know why yet. Now you are
confirming that suspicion. We need to remove them from the jar.
Could you please open a bug report? I'll make the change in the Ant
script and make sure it doesn't break the client-tier apps.
Andrus
On Oct 31, 2005, at 4:17 PM, Tore Halset wrote:
> Hello.
>
> I am trying to use nodeps-1.2M6 in my app deployed on a plain
> jboss-4.0.3. I am switching to nodeps because of a log4j version
> conflict. Still I get the following error:
>
> java.lang.LinkageError: loader constraints violated when linking
> org/apache/log4j/Priority class
> org.objectstyle.cayenne.util.ResourceLocator.<clinit>
> (ResourceLocator.java:94)
> org.objectstyle.cayenne.conf.DefaultConfiguration.<init>
> (DefaultConfiguration.java:111)
> org.objectstyle.cayenne.conf.DefaultConfiguration.<init>
> (DefaultConfiguration.java:90)
>
> I tracked this down to the fact that even nodeps-1.2M6 has two
> log4j classes boundled.
>
> jar tvf cayenne-nodeps-1.2M6.jar | grep log4j
> 0 Thu Oct 06 17:06:04 CEST 2005 org/apache/log4j/
> 1740 Mon Nov 01 21:21:04 CET 2004 org/apache/log4j/Level.class
> 2632 Mon Nov 01 21:21:04 CET 2004 org/apache/log4j/Priority.class
>
> After removing the log4j-classes from the cayenne-nodeps jar the
> LinkageError got away and everything worked ok.
>
> Should I register this as a bug or is it part of the 1.2-moving
> target or is it fixed in cvs?
>
> Regards,
> - Tore.
>
>
>
>
This archive was generated by hypermail 2.0.0 : Mon Oct 31 2005 - 11:40:30 EST