It's 21st century, use Maven!
It will download ONLY the needed jars.
On Tue, Jul 26, 2011 at 4:10 AM, eugenebalt wrote:
> I resolved all my issues, but I had to add a ton of JAR's that were never
> mentioned anywhere. Thanks anyway.
>
> --
> View this message in context:
> http://apache-wicket.1
put just "slf4j-simple-1.6.1.jar" and "slf4j-api-1.6.1.jar" in WEB-INF/lib
> -Original Message-
> From: eugenebalt [mailto:eugeneb...@yahoo.com]
> Sent: Tuesday, 26. July 2011 03:10
> To: users@wicket.apache.org
> Subject: Re: Problems with Wicket J
Eugene,
Usually you just need one jar from SLF4J in order to statically make the
bridge to the logging system of choice.
On Mon, Jul 25, 2011 at 10:10 PM, eugenebalt [via Apache Wicket] <
ml-node+3694554-1008203965-65...@n4.nabble.com> wrote:
> I resolved all my issues, but I had to add a ton
I resolved all my issues, but I had to add a ton of JAR's that were never
mentioned anywhere. Thanks anyway.
--
View this message in context:
http://apache-wicket.1842946.n4.nabble.com/Problems-with-Wicket-JARs-jcl-over-slf4j-tp3694328p3694554.html
Sent from the Users forum mailing list archive a
Sorry for posting further on this, but I managed to fix the LogFactory by
using common-logging-api.jar, and now I have a new problem that Wicket is
complaining about:
org.apache.velocity.app.Velocity not found
Why do I need to add Velocity to my project?
--
View this message in context:
http://
Note that if I remove jcl-over-slf4j, then I get another exception, it can't
find the LogFactory class.
java.lang.NoClassDefFoundError: org/apache/commons/logging/LogFactory
I'm just surprised none of these problems are mentioned anywhere. I'm a
Wicket beginner who added the Wicket JARs and the S
