I am not feeling well enough to deal with this right now. However, as soon as I get better and have the opportunity I'll fix whatever needs fixing.

I hope that's OK with you.

Cheers,

At 03:53 PM 5/11/2006, Jim Jagielski wrote:
Works fine for me (with 1.5).

On May 9, 2006, at 10:31 PM, Gianmaria Clerici wrote:


Just want to confirm that everything works just fine with 1.5


-----Original Message-----
From: Gianmaria Clerici [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 7:14 PM
To: Apache Directory Developers List
Subject: RE: [ApacheDS] Problem with nlog4j


Yes I was using 1.4.2_04.
I didn't see the requirement to use 1.5.

I just downloaded 1.5 and I am rebuilding now.
Will let you know how it goes.

-----Original Message-----
From: Alex Karasulu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 5:35 PM
To: Apache Directory Developers List
Subject: Re: [ApacheDS] Problem with nlog4j

Question:

What JDK are you building with?  I suspect 1.4.X and if so this means
that nlog4j was not compiled
with backwards compatibility with 1.4.  If so then we're in a world of
hurt since we'll have to contact
Ceki (slf4j maintainer), upgrade to the next release and re-release
everything that depended on this jar.

Alex

Gianmaria Clerici wrote:
I removed the entire directory and got it again from SVN.
I also removed everything under .m2/repository.

I still get the same error.
I am attaching the output of the build from scratch.

But it's the same error as before:


[ERROR] BUILD FAILURE

[INFO]
---------------------------------------------------------------------- --

[INFO] Compilation failure

c:\Bridgestream\Apache_Directory\releases\apacheds\1.0-RC3\server- main\s
rc\main\java\org\apache\directory\server\Service.java:[33,-1] cannot
access org.slf4j.Logger

bad class file: C:\Documents and
Settings\gclerici\.m2\repository\org\slf4j\nlog4j\1.2.24 \nlog4j-1.2.24.j
ar(org/slf4j/Logger.class)

class file has wrong version 49.0, should be 48.0





[INFO]
---------------------------------------------------------------------- --

[INFO] Trace

org.apache.maven.BuildFailureException: Compilation failure

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Default
LifecycleExecutor.java:555)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLif ec
ycle(DefaultLifecycleExecutor.java:475)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecyc le
(DefaultLifecycleExecutor.java:891)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle (Defaul
tLifecycleExecutor.java:729)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Default
LifecycleExecutor.java:505)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneG oa
l(DefaultLifecycleExecutor.java:488)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal (DefaultL
ifecycleExecutor.java:458)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHand le
Failures(DefaultLifecycleExecutor.java:306)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegment s(
DefaultLifecycleExecutor.java:219)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute (DefaultLifec
ycleExecutor.java:140)

        at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)

        at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)

        at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)

        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

        at
sun.reflect.NativeMethodAccessorImpl.invoke (NativeMethodAccessorImpl.jav
a:39)

        at
sun.reflect.DelegatingMethodAccessorImpl.invoke (DelegatingMethodAccessor
Impl.java:25)

        at java.lang.reflect.Method.invoke(Method.java:324)

        at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)

        at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)

        at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)

        at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

Caused by: org.apache.maven.plugin.CompilationFailureException:
Compilation failure

        at
org.apache.maven.plugin.AbstractCompilerMojo.execute (AbstractCompilerMoj
o.java:505)

        at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)

        at
org.apache.maven.plugin.DefaultPluginManager.executeMojo (DefaultPluginMa
nager.java:412)

        at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals (Default
LifecycleExecutor.java:534)

        ... 20 more

[INFO]
---------------------------------------------------------------------- --

[INFO] Total time: 9 minutes 14 seconds

[INFO] Finished at: Tue May 09 15:03:09 PDT 2006

[INFO] Final Memory: 7M/18M

[INFO]
---------------------------------------------------------------------- --


-----Original Message-----
From: Alex Karasulu [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 09, 2006 1:00 PM
To: Apache Directory Developers List
Subject: [ApacheDS] Problem with nlog4j (was: Re: [ApacheDS] 1.0-RC3
Released)

Gianmaria,

Gianmaria Clerici wrote:

I just got the code from SVN and I tried to do a build but it fails
with this error.

Works like a champ for me on a new fresh clean build with maven repos
blown away.

It download the jar file but then it's complaining that it's not the
correct version.

Hmmm you might have had issues on transfer of the nlog4j jar.  Please
try again.

Also please try to use a fresh new subject when you start a new
thread.

Alex



--
Ceki Gülcü
http://ceki.blogspot.com/

Reply via email to