Yes but Raja has made it clear that he wants no repositories whatsoever... I think Maven is the wrong tool if you are *that* against repos, but who am I to say what others should do...
Wayne On 4/3/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Note that you can create your own internal repository[1] and reference that > within pom.xml[2]. You do not need to (and in fact, in most cases should > not) deploy[3] your artifact to the central Maven repository[4]. > > > HTH, > Ian > > [1] > http://maven.apache.org/guides/introduction/introduction-to-repositories.html* > [2] > http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_repository > [3] http://maven.apache.org/guides/mini/guide-ibiblio-upload.html > [4] http://repo1.maven.org/maven2 > > * It would be nice if the core documentation (Guides, Introductions, etc) > included anchors to the major sections for ease of reference > > It's better to be hated for who you are > than loved for who you are not > > Ian D. Stewart > Appl Dev Analyst-Advisory, DCS Automation > JPMorganChase Global Technology Infrastructure > Phone: (614) 244-2564 > Pager: (888) 260-0078 > > > > "Wayne Fay" > <[EMAIL PROTECTED] To: "Maven Users List" > <users@maven.apache.org> > om> cc: > Subject: Re: sharing artifacts > without repositories??? > 04/01/2006 11:32 > AM > Please respond to > "Maven Users > List" > > > > > > Use <scope>system</scope> everywhere. > > Good luck managing it. > > Wayne > > On 4/1/06, Kenney Westerhof <[EMAIL PROTECTED]> wrote: > > On Sat, 1 Apr 2006, raja bangaru wrote: > > > > You can't. Repositories are a core maven concept; it is the only way to > > share artifacts. > > > > Why don't you want to put A in a repository? > > > > (mvn install -> local repository, no problem, right? it's just a > > 'temporary' directory anyway). > > > > -- Kenney > > > > > I find that we can share any number of artifcats withing mulitple > projects > > > thru the repository. > > > i mean we can take repository as a common place,... > > > For example, > > > If the built artifact of project A is to be needed for another project > > > B,..we can place the built artifact of A in the repository so that > > > project B can use it.. > > > > > > My question : > > > > > > What if i dont want to put the built artifact of Project A in a > repository > > > and still it should be available to my project B > > > > > > > > > Any maven goals to handle this scenario??? > > > > > > > > > > > > Thanks, > > > Raja. > > > > > > > -- > > Kenney Westerhof > > http://www.neonics.com > > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > > > --------------------------------------------------------------------- > > 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] > >
