On Thu, Apr 17, 2014 at 1:43 PM, Igor Fedorenko <[email protected]> wrote:
> My problem with current behaviour is that the same location is used as > both cache for remote artifacts and repository for locally installed > artifacts. I think a cleaner model is to separate the two. It will still > be possible to install locally, although I am not sure we'll need > separate "install" phase. > +1 Jeff > > -- > Regards, > Igor > > > On 2014-04-17, 7:13, 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). >> >> Just my two cents, Robert >> >> Robert Patrick <[email protected]> VP, FMW Platform >> Architecture Oracle Mobile: +1 469 556 9450 Sent from my iPad > >> >>> On Apr 17, 2014, at 1:54 AM, Baptiste Mathus <[email protected]> wrote: >>> >>> 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" <[email protected]> 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 <[email protected]> >>>>> Date: 2014-04-15 10:12 GMT+02:00 >>>>> Subject: Re: Why Is Maven Ignoring My Local Repo? >>>>> To: Maven Users List <[email protected]> >>>>> >>>>> >>>>> 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 <[email protected]> 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: [email protected] >>>>>> For additional commands, e-mail: [email protected] >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Jeff MAURY "Legacy code" often differs from its suggested alternative by actually working and scaling. - Bjarne Stroustrup http://www.jeffmaury.com http://riadiscuss.jeffmaury.com http://www.twitter.com/jeffmaury
