> So how then does one know when they have to purge the local > repository? Having rules where you sometimes need to and > sometimes don't is really hard to live with. Perhaps you can > clarify the rules?
I can provide a bit of clarify here. You could have a problem if you changed the artifactId, groupId or version of anything in your project. Maven would install a new copy of this artifact in your local and if you happen to forget to update all references to this dependency, your code will still build and compile file, but you may get unexected runtime problems. If you purge your local, your build will properly fail. > And if it's important why isn't it done by > default? This is a good question which I am not qualitfied to answer. I have been tempted to add to the clean phase a goal which also deletes the artifact from the local repo (although this still isn't sufficient). --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
