Thanks for looking into this! It is fixed, but I doubt this can be fixed automatically in the release script, as the mvn release:update-versions functionality doesn't update the dependencies to the newer versions, and it looks like the version-maven-plugin won't help either (though I'd like to be proven wrong here).
Martijn On Fri, Sep 28, 2012 at 12:38 PM, Andreas Kuhtz <andreas.ku...@gmail.com> wrote: > The wicket-examples/pom.xml has a fixed old version (0.4-SNAPSHOT instead of > 0.5-SNAPSHOT) for the wicket-atmosphere artefact ... > > The wicket-experimental/wicket-native-websocket/pom.xml has a fixed old > version (0.3-SNAPSHOT instead of 0.4-SNAPSHOT) for the wicket- > native-websocket-core artefact ... > > The wicket-experimental/wicket-examples-parent/wicket-examples-jar/pom.xml > has a fixed old version (0.4-SNAPSHOT instead of 0.5-SNAPSHOT) for the > wicket-atmosphere artefact ... > > The wicket-experimental/ pom.xml has a fixed old version (0.3-SNAPSHOT > instead of 0.4-SNAPSHOT) for the wicket-bootstrap, wicket-examples-jar (jar, > sources) and wicket-examples-war artefact ... > > > > > > -- > View this message in context: > http://apache-wicket.1842946.n4.nabble.com/6-x-config-seems-broken-tp4652438p4652489.html > Sent from the Forum for Wicket Core developers mailing list archive at > Nabble.com. -- Become a Wicket expert, learn from the best: http://wicketinaction.com
