slf4j is a project which allows a project to implement logging, and the
user of that project to decide which actual logging implementation to use.
See http://slf4j.org/
Met vriendelijke groet,
Kind regards,
Bas Gooren
Op 9-2-2013 14:59, schreef Stephen Walsh:
Looked like there were some othe
Looked like there were some other items I needed to upgrade as well: maven
compiler plugin, junit.
There was one called sfl40j or similar. What is this used for?
Thanks again for help! Learning a lot from you guys. Hope to contribute back
once I really start understanding. New to java and wi
Also upgrade your maven-eclipse-plugin to use 2.9. Works much better on OS X.
Martijn
On Fri, Feb 8, 2013 at 12:08 AM, Stephen Walsh
wrote:
> This was the answer, Gabriel! Because my computer only has one JRE (1.6
> with dev docs) installed, Eclipse was using it, but it appeared as though I
> w
This was the answer, Gabriel! Because my computer only has one JRE (1.6
with dev docs) installed, Eclipse was using it, but it appeared as though I
was using 1.5.
This minor change to my pom.xml solved it though! Thank you!
___
Stephen Walsh | http://connectw
Hi Stephen,
This did happen to me once!
Did you check in your pom.xml that your source and target attributes are 1.6
?
org.apache.maven.plugins
maven-compiler-plugin
That's what I figured. I've now discovered that Maven isn't finding rt.jar
because I'm developing on a Mac. Mac Java doesn't use rt.jar it uses
classes.jar.
[INFO] --- maven-eclipse-plugin:2.8:eclipse (default-cli) @ campingawaits
---
[INFO] Using Eclipse Workspace: /Users/stephen/Documents/work
Hi,
Wicket 1.5 is built with Java 1.5.
Wicket 6 with Java 6
Wicket 7 will most probably with JDK 7
Wicket source code doesn't have anything that can talk to Eclipse or any
other IDE :-)
On Thu, Feb 7, 2013 at 6:16 PM, Stephen Walsh wrote:
> I'm using Eclipse Juno to develop my wicket app, and
I'm using Eclipse Juno to develop my wicket app, and what I've noticed is
that the JRE keeps switching back to 1.5 instead of staying on 6. I've
tried changing this in the build path and pointing it to the developer
version of Java 6 multiple times.
I'm wondering if there's a setting somewhere in