Re: 1.3.0-beta2/3 broken in the m2 repo?
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 wicket-extensions you can add the following to your pom: org.apache.wicket wicket-extensions 1.3.0-beta3 In this case you *could* remove the wicket dependency itself, because the transitive dependency management of Maven will pull it in for you. Martijn On 9/12/07, Craig Tataryn <[EMAIL PROTECTED]> wrote: > 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-like" nature of > resolving a dependency and all of it's dependencies, and so on. > > Craig. > > On 9/12/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > > > 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 PROTECTED]> wrote: > > > 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 download directly from: > > > http://mvnrepository.com/artifact/org.apache.wicket/wicket-parenteither. > > > > > > Not sure if it was someone on the list here that did the initial > > install, if > > > so, could you take a look? > > > > > > Craig. > > > > > > > > > -- > > Buy Wicket in Action: http://manning.com/dashorst > > Apache Wicket 1.3.0-beta3 is released > > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.3.0-beta2/3 broken in the m2 repo?
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-like" nature of resolving a dependency and all of it's dependencies, and so on. Craig. On 9/12/07, Martijn Dashorst <[EMAIL PROTECTED]> wrote: > > 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 PROTECTED]> wrote: > > 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 download directly from: > > http://mvnrepository.com/artifact/org.apache.wicket/wicket-parenteither. > > > > Not sure if it was someone on the list here that did the initial > install, if > > so, could you take a look? > > > > Craig. > > > > > -- > Buy Wicket in Action: http://manning.com/dashorst > Apache Wicket 1.3.0-beta3 is released > Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: 1.3.0-beta2/3 broken in the m2 repo?
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 PROTECTED]> wrote: > 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 download directly from: > http://mvnrepository.com/artifact/org.apache.wicket/wicket-parent either. > > Not sure if it was someone on the list here that did the initial install, if > so, could you take a look? > > Craig. > -- Buy Wicket in Action: http://manning.com/dashorst Apache Wicket 1.3.0-beta3 is released Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.3.0-beta3/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 1.3.0-beta2/3 broken in the m2 repo?
"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-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 download directly from: > http://mvnrepository.com/artifact/org.apache.wicket/wicket-parent either. > > Not sure if it was someone on the list here that did the initial install, > if so, could you take a look? > > Craig. >
1.3.0-beta2/3 broken in the m2 repo?
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 download directly from: http://mvnrepository.com/artifact/org.apache.wicket/wicket-parent either. Not sure if it was someone on the list here that did the initial install, if so, could you take a look? Craig.
