File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
The moose likes Blog around the Campfire and the fly likes Maven: Don’t just blindly “mvn clean install” Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


JavaRanch » Java Forums » Other » Blog around the Campfire
Bookmark "Maven: Don’t just blindly “mvn clean install”" Watch "Maven: Don’t just blindly “mvn clean install”" New topic
Author

Maven: Don’t just blindly “mvn clean install”

Marco Behler
Greenhorn

Joined: Jun 01, 2014
Posts: 1
Suppose you have a multi-module Maven project, with a ton of modules, two of them being fancynewtool-db and fancynewtool-rest. fancynewtool-rest has fancynewtool-db as a dependency. What happens if you cd into the rest-module and do a mvn clean compile/test for the first time? Maven will tell you that it cannot resolve the db-module dependency. And now your instinct might be to do a blind mvn clean install in the parent project, because that is just the way Maven works ™.

A full mvn clean install works, but is simply not the fastest and most efficient way. Read more...
 
GeeCON Prague 2014
 
subject: Maven: Don’t just blindly “mvn clean install”