ROBERT PATRICK wrote: > I don't understand the issue. I regularly use artifacts in my build that > are only present in my local repository. Yes, Maven checks my remote > repository for these artifacts but it doesn't ignore them if they are not > in the remote repo. It also works when building offline without access to > my remote repository. Is it treated as a cache, maybe so but it's not > clear to me that renaming the tag won't serve to add more confusion to a > long-standing behavior... > > Clearly, removing the ability to install artifacts locally would be a very > bad idea since it would make it more difficult for casual users to use > Maven for casual builds (e.g., I regularly use it to build sample projects > for customers that I never intend to do anything else with once I send it > to the customer).
A remote repository is specified with an URL. Nobody prevents you from using a file URL i.e. having a real local repository on your disk. - Jörg --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org