> -----Original Message----- > From: Stephen Nesbitt [mailto:[EMAIL PROTECTED] > Sent: Tuesday, November 23, 2004 1:14 AM > To: [EMAIL PROTECTED] > Cc: Vincent Massol > Subject: Re: [PROPOSAL] Ading a new tag to <dependency>? > > > On Sunday 21 November 2004 02:14, Vincent Massol wrote: > > Hi Maven devs, > > > > I think there's a need to allow specifying when some artifacts > > are only to be looked for in the local repository. For example, > > in a multiproject the local repository is used to share private > > artifacts between the subprojects. These private artifacts are > > not meant to be uploaded to a Maven remote repo. > > > [..]
> I noticed that J�rg Schaible's post kinda made the same point with > the suggestion of a <repository> tag in the dependency element. > > Hows does any of this fit into"in situ" artifacts? In situ artifact won't be that helpful in that case if it comes to speed of processing. Other m2 feature might be helpful - you can define a repositories per project basis. IT means that each pom can contain the location from which corresponding jar should be taken and you just need to push your poms to right repositoriy(ies) In m2 we have limited the number of repositories into which you can deploy artifact to 1. That's is probaably something which we may can revisit in case it will be really needed as I also see a need of having distinct repositories for snapshots artifacts and released artifacts. We can probably search for solution here. But first we have to be ready with more fundental things as the processing model in m2 is bit different mainly due to introduction of transitive dependencies and it might be that we will find different bottlnecks and while we will be searching for the solution which will remove them also this problem will be gone. But such use cases like yours are definitly helpful for us as definitly large teams of devlopers are using maven differently then we do internally among maven devlopers. Michal --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
