To depend on Wicket you need to add the following two dependencies:
org.apache.wicket
wicket
1.3.0-beta3
org.slf4j
slf4j-log4j12
1.4.0
(the latter only if you want to use log4j as a logging implementation,
which is what about 99% of our users want).
If you want to use
Interesting. Well I assumed that by depending on it, it would pull in all
the right dependencies. You see, when you just link to groupId=
org.apache.wicket artifactId=wicket you don't get any dependencies and
ultimately your webapp fails.
In my mind the power of maven is to provide that "yum-lik
there are 2 things wrong with your approach:
1. wicket-parent is not a jar, so you should have used an additional
pom
2. wicket-parent is not a jar, so you should not try to depend on it
in the first place
Why are you trying to depend on wicket-parent?
Martijn
On 9/12/07, Craig Tataryn <[EMAIL
"Does work when trying to download directly from"
Meant "Doesn't" not Does.
On 9/11/07, Craig Tataryn <[EMAIL PROTECTED]> wrote:
>
> Tried grabbing:
>
>
> org.apache.wicket
> wicket-parent
> 1.3.0-beta3
>
>
> And then:
>
>
> org.apache.wicket
> wicket-parent
> 1.3.0-bet
Tried grabbing:
org.apache.wicket
wicket-parent
1.3.0-beta3
And then:
org.apache.wicket
wicket-parent
1.3.0-beta2
Each bomb with the "Failed to resolve artifact.Missing:1)
org.apache.wicket:wicket-parent:jar:1.3.0-beta2" (same for beta3).
Does work when trying to do
