I also think that installing locally is somehow to be seen as a hack. And though I do it myself on a regular basis while developing, I indeed never see it as a sustainable place for my artifacts, only deploy is (and still temporary for non releases).
Yes, I think we should rename that tag. And if not we should stop telling people it must not be seen as a repository, but as a cache... Le 15 avr. 2014 11:32, "Igor Fedorenko" <i...@ifedorenko.com> a écrit : > > <localRepository> currently works as both a cache or artifacts from > remote repositories and as a repository of locally installed artifacts. > Do you suggest we get rid of "locally installed" functionality (which I > personally very much in favour) or you want to just change the name > (which I think will be confusing)? > > -- > Regards, > Igor > > On 2014-04-15, 4:53, Baptiste Mathus wrote: > >> Hi all, >> >> Wondering, though not strictly 4.0.0 restricted, shouldn't a decision be >> made about that vocabulary and reflect this in the docs and settings.xml >> tags and so on? >> >> I mean, I myself often explain it's not really a local repo, more a cache, >> but the tag names and the docs makes it hard to spread the word. >> >> In settings.xml : <localRepository> could be renamed to <localCache> or >> <localRepositoryCache> ? >> >> In the docs, e.g. https://maven.apache.org/pom.html there're many >> references to a "local repository". >> >> WDYT? >> >> Cheers >> >> ---------- Forwarded message ---------- >> From: Stephen Connolly <stephen.alan.conno...@gmail.com> >> Date: 2014-04-15 10:12 GMT+02:00 >> Subject: Re: Why Is Maven Ignoring My Local Repo? >> To: Maven Users List <us...@maven.apache.org> >> >> >> It's not a local repository. It is a local repository cache. >> >> There are files there that record where the artifacts were cached *from*. >> >> If the artifact is there but the cache file is not or indicates a >> different >> source from the allowed sources for your build, then Maven will ignore the >> artifact in your cache and check the remote sources. >> >> >> On 15 April 2014 02:02, Eric Kolotyluk <e...@kolotyluk.net> wrote: >> >> I seem to keep running into this problem regularly for things not in >>> Maven >>> Central >>> >>> [ERROR] Failed to execute goal >>> >> org.apache.maven.plugins:maven-site-plugin:3.3:site >> >>> (default-site) on project csharp-windows-elevate: Execution default-site >>> >> of >> >>> goal org.apache.maven.plugins:maven-site-plugin:3.3:site failed: Plugin >>> org.apache.maven.plugins:maven-site-plugin:3.3 or one of its >>> dependencies >>> could not be resolved: Could not find artifact >>> >> net.trajano.wagon:wagon-git:jar:1.0.1-SNAPSHOT >> >>> in local-nexus (http://localhost:8081/nexus/content/groups/public) -> >>> [Help 1] >>> >>> I can see the artifact in my local repo, but maven somehow feels, because >>> it cannot find it in my nexus repository, then it does not exist. >>> >>> The side problem is, even though nexus can see the artifact in its index, >>> it refuses to download it. >>> >>> Why do maven and nexus work so hard at ignoring artifacts? >>> >>> Cheers, Eric >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> >> >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
