<repositories> <repository> <id>wicket</id> <url>http://wicketstuff.org/maven/repository/</url> </repository> </repositories> That's the only changes I made to the working 1.3.0-beta3 based pom.
Regards, Sebastiaan Johan Compagner wrote:
hmm are the parent poms not deployed somehow what kind of build triggers that exactly? johan On 9/11/07, Sebastiaan van Erk <[EMAIL PROTECTED]> wrote:Hi, I'm trying to use the latest snapshot version of wicket, but maven complains: [INFO] snapshot org.apache.wicket:wicket:1.3.0-SNAPSHOT: checking for updates from wicket Downloading: http://wicketstuff.org/maven/repository//org/apache/wicket/wicket/1.3.0-SNAPSHOT/wicket-1.3.0-SNAPSHOT.pom 1/2K 2/2K 2K downloaded [INFO] snapshot org.apache.wicket:wicket-jdk14:1.3.0-SNAPSHOT: checking for updates from wicket Downloading: http://wicketstuff.org/maven/repository//org/apache/wicket/wicket-jdk14/1.3.0-SNAPSHOT/wicket-jdk14-1.3.0-SNAPSHOT.pom [ERROR] An error occurred during dependency resolution of the following artifact: org.apache.wicket:wicket:1.3.0-SNAPSHOT Caused by: Unable to get dependency information: Unable to read the metadata file for artifact 'org.apache.wicket:wicket:jar': Cannot find parent: org.apache.wicket:wicket-jdk14 for project: null:wicket:jar:null org.apache.wicket:wicket:jar:1.3.0-SNAPSHOT from the specified remote repositories: wicket (http://wicketstuff.org/maven/repository/), central (http://repo1.maven.org/maven2) Am I doing something wrong? Regards, Sebastiaan
smime.p7s
Description: S/MIME Cryptographic Signature