Ahh, your right. I'm doing this within eclipse and for some reason
was just assuming I was getting all of trunk. But I think I'm just
updating all the projects, not updating the root. Now that you
mention it, I'm sure it will work.
Thanks!
On 10/30/07, Martijn Dashorst <[EMAIL PROTECTED]> wro
Do a install from the root
your parent pom is not up to date in the local repo
Martijn
On 10/30/07, Tauren Mills <[EMAIL PROTECTED]> wrote:
> I just updated from svn again and I'm still having this problem. I've
> checked out the entire wicket trunk including jdk-1.4 and jdk-1.5. I
> just upda
I just updated from svn again and I'm still having this problem. I've
checked out the entire wicket trunk including jdk-1.4 and jdk-1.5. I
just updated and did the following:
cd wicket/jdk-1.4/wicket
mvn install -Dmaven.test.skip=true
But this complains of dependencies missing versions. It wor
Have you checked out the entire wicket source tree - that contains
jdk14, jdk15 etc? If not then maybe the individual poms cannot find
the parent pom that defines those version variables.
On 11 Oct 2007, at 22:46, Tauren Mills wrote:
I just updated wicket, wicket-extensions and wicket-exam
I just updated wicket, wicket-extensions and wicket-examples from
trunk. When I tried to run mvn install eclipse:eclpise, I got errors
stating that there were dependencies missing versions. So I added
versions to the pom.xml for wicket and wicket-examples. Now mvn runs.
Am I doing something wrong
