Maven2 handles transitive dependencies, meaning that if a project you
are dependent on is dependent on other projects, Maven will add them to
the classpath. So that's why you didn't have to add that jar manually,
Maven did it for you. I don't think Maven1 had this functionality.
Linda
Stephen Swinsburg wrote:
Thanks Adriano. I don't seem to need that for my Maven2 build though,
is there a reason for that? I'll try that though.
cheers,
Steve
On 12/03/2009, at 8:02 PM, Adriano dos Santos Fernandes wrote:
Steve Swinsburg escreveu:
Hi all,
I have a need to backport my wicket app that builds perfectly in
Maven2 to Maven1. I think I've adjusted all the pom.xml to
project.xml correctly as all the classes and dependent jars looks
like they are where they need to be, but on startup I get this:
java.lang.NoClassDefFoundError: org/slf4j/LoggerFactory
Although in my WEB-INF/lib I have (amongst the others) the required
jars:
slf4j-log4j12-1.4.2.jar
log4j-1.2.14.jar
Any idea what's missing? Does anyone else build under Maven1?
You also need slf4j-api-*.jar.
Adriano
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
------------------------------------------------------------------------
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.5.278 / Virus Database: 270.11.10/1996 - Release Date: 03/11/09 20:42:00
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
