Thanks for all the info. It seems like the appropriate solution is to use the central repository to get access to common jars and then setup my own "remote" repository that I can use a central location to publish my project artifacts.
On a slightly different subject but related to Maven I'm trying to figure out the best approach to take in terms of integrating CVS into my projects. I can see already that I'm going to have lots of little maven projects and each project should be able to have its own branches and versions in the repository. Does this mean that I set up a separate repository for each project or can I still accomplish this using one repository in CVS? thanks dkrebs ----- Original Message ----- From: "STRAYER, JON (SBCSI)" <[EMAIL PROTECTED]> To: "Maven Users List" <[EMAIL PROTECTED]> Sent: Thursday, November 04, 2004 8:11 AM Subject: RE: 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? Sort of. You would just publish to your own repository, but you can still use the public one for downloads. --------------------------------------------------------------------- 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]
