On Thu, 31 Jan 2008 01:56:09 Mark Hobson wrote: > On 30/01/2008, Mark Hobson <[EMAIL PROTECTED]> wrote: > > I don't think that linking this level of artifact resolution > > uncertainty to its source repository is a good idea. How version > > ranges are resolved should be completely deterministic and independent > > from where the artifact was actually downloaded from, otherwise we'll > > end up with no end of build reproducibility problems. fair enough
> > In addition, the local repository would be exempt from these rules. I think the local repository should be treated just like any repo and separate from the cache of remote repositories... this is actually the cause of _many_ problems in thats its always included... > This would require manually deleting artifacts from the local repo to > ensure that certain versions weren't picked up; a maintenance > nightmare I'm sure you'll agree. which is bloody annoying if I was able to configure my release profiles to not include the local repository that would be much better because I would only get released artifacts in remote repositories > > How's best to proceed with resolving this issue? Would voting make > sense, or should the PMC lay down the intended direction? I'm not > sure whether this thread needs to get any longer.. :) open to a vote > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
