In addition to this, if you are lazy (like me) and have smb or similar access to the repository you want to publish to, you can always set your local repository and remote to be the same thing. (Note: in a team environment, this is not such a great idea, but if you are working alone, its it).
Hope you dont mind, semi-useless advice :-) -Corey On Thu, 4 Nov 2004 10:52:37 +0100, Maczka Michal <[EMAIL PROTECTED]> wrote: > > > > -----Original Message----- > > From: Duncan Krebs [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 04, 2004 2:36 AM > > To: Maven UserList > > Subject: Project Distribution Process > > > > > > Hi, > > I've been working on implementing Maven into my build process > > and was wondering how to go about a couple of things. > > > > When I build a distribution of a project I want Maven to put > > that newly compiled jar into a central repository so that > > other projects can reference to it in project.xml. Would this > > newly created jar go into the same repository that holds all > > my third party jars? If thats the case then I'd have to > > create my own central repository and not use the public one? > > > If you work alone you may just stick to your local repository. If you share > your work (aars) with others > you may want to setup your remote repository. Note that the name "central" > repository is used to refer to the repository > hosted at ibiblio. There could be only one central repository - in your case > the correct term is _remote_ repository. > > Michal > > --------------------------------------------------------------------- > 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]
