Hi
I guess it's because of the pom file changes, which introduced a parent
pom file in branch/WICKET_1_2.
See Martijn's announcement here:
http://www.nabble.com/New-pom-structure-tf1870006.html
Regards
Frank
On Tue, 2006-07-04 at 19:50 -0700, Jonathan Locke wrote:
>
> i have current wicket
i have current wicket 1.2 head and maven 2.0.4.does anyone have any idea why i would get the exception below?should i be using a different repo or something?thanks, jonC:\Projects\voicetribe\workspace\wicket>mvn install
[INFO] Scanning for projects...[INFO] --