File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Ant, Maven and Other Build Tools and the fly likes Maven:  How to upgrading Wicket version Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » Ant, Maven and Other Build Tools
Bookmark "Maven:  How to upgrading Wicket version " Watch "Maven:  How to upgrading Wicket version " New topic
Author

Maven: How to upgrading Wicket version

Frank Silbermann
Ranch Hand

Joined: Jun 06, 2002
Posts: 1390
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?

Peter Johnson
author
Bartender

Joined: May 14, 2008
Posts: 5845
    
    7

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:



JBoss In Action
Frank Silbermann
Ranch Hand

Joined: Jun 06, 2002
Posts: 1390
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
Bartender

Joined: May 14, 2008
Posts: 5845
    
    7

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).
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: Maven: How to upgrading Wicket version