Hello,
Your point is interesting , but I really think theres more to this than
simple convenience.
I am really interested in this because I think its a bug.
Its you choice if you want to have a big fat war (~5MB) and deploy that over
scp - i guess the fast deploy cycles go out the window,
or
Hello,
I have a problem with the wicket - spring integration in wicket 1.4 rc2 , i
think its similar to https://issues.apache.org/jira/browse/WICKET-1848
The use case is like this :
I have 2 simple applications running in a jetty server.
To keep things simple , i added the spring and wicket
IMHO sharing JARs across J2EE apps is not worth the trouble.
- it messes up some JARs (commons-logging is a classic example)
- it forces you to keep your dependent JAR versions in sync across
applications. This is particularly important in an enterprise
environment where changing a dependent
