• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Jeanne Boyarsky
  • Tim Cooke
Sheriffs:
  • Liutauras Vilda
  • paul wheaton
  • Henry Wong
Saloon Keepers:
  • Tim Moores
  • Tim Holloway
  • Stephan van Hulst
  • Carey Brown
  • Frits Walraven
Bartenders:
  • Piet Souris
  • Himai Minh

Maven: How to upgrading Wicket version

 
Ranch Hand
Posts: 1408
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Not quite a year ago I followed the instructions in http://herebebeasties.com/2007-10-07/wicket-quickstart/ to download and build the Wicket Quickstart project (essentially a "Hello World" application). I then manipulated this project into the application I needed.

The .pom file provided contained "<version>${wicket.version}</version>" for the versions of three dependencies -- wicket, wicket-extensions and wicket-datetime. It downloaded version 1.3.3 of the three .jar files, as that was the latest version at the time. I manipulated the Quickstart project into my own application.

Now I would like to upgrade to version 1.3.5 -- how do I do that? Do I have to change the definition of the variable ${wicket.version} and re-compile? If so, where would I find that variable -- it is not in my .POM file.

What do I need to do so that Maven will download version 1.3.5 of the Wicket .jars and use it to rebuild my project?

 
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Is the "wicket.version" property being set somewhere in the pom? Or perhaps in a master pom?

Of course, one thing you could do is simply:

 
Frank Silbermann
Ranch Hand
Posts: 1408
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Peter Johnson wrote:Is the "wicket.version" property being set somewhere in the pom? Or perhaps in a master pom?

Of course, one thing you could do is simply:

Thanks! I also had to "mvn clean" before it would do anything.

But I'm kind of curious as to where the ${wicket.version} variable is being set. Or does it select the most recent version in the local repository? (If so, it seems like there would be a command to update the local repository independently of whether a project is calling for a new version.)
 
Peter Johnson
author
Posts: 5856
7
Android Eclipse IDE Ubuntu
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
The syntax to use the latest version is:



Effectively, this means the latest version from 1.3.5 on. The property value must be set somewhere in the Maven pom or its included poms, or from some global setting (settings.xml).
 
If somebody says you look familiar, tell them you are in porn. Or in these tiny ads:
Free, earth friendly heat - from the CodeRanch trailboss
https://www.kickstarter.com/projects/paulwheaton/free-heat
reply
    Bookmark Topic Watch Topic
  • New Topic