Hi Sander, Glad you figured it out. Local repositories are for local use..
Since you're setting up a maven environment for your teams, here are some tips.. You'll want to setup a company-wide shared repository via ftp/scp/whatever and put a webserver in front of it. This will be the repository where developers - after defining the repository in settings.xml or pom.xml - will automatically look for artifact updates and missing dependency libraries. It's a good idea to setup a snapshot repository as well, you can can periodically clear this repository since frequent snapshot installs can quickly fill up the disk quota. With the webserver for your shared repositories in place, you have everything needed to host your maven project's website and QA reports.. So you might want to setup distributionManagement in your projects for this as well.. Keeps the docs in sync and the project managers, testers, implementors, etc.. happy ;) You may also want to take a look at maven-proxy to centralize the repository access of released artifacts for your teams. This reduces per-user/project repository configuration and internet access for library downloads.. And while you're at it.. You really want to check out continuum at http://maven.apache.org/continuum/. Continuous integration just feels right and easy with maven, it can automatically keep your website, shared artifacts and container-deployed applications up-to-date with minor effort.. Happy hacking! Jo On 2/26/07, Sander Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
Hi Jo, Thanks for the help. I thought the local repository was from a team perspective instead of per developer. Cheers, Sander -- View this message in context: http://www.nabble.com/Multiple-developer-dependency-management-tf3284959s177.html#a9162023 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
