> I am a bit confused about what you said. The page says : > However the repositoryDefinitions profile section can be made > simpler by using a proxy infront of the internal repositories. > > What I understand from this (and which sounds obvious to me) is: if you're > using maven-proxy, you don't have to put those profile definitions in your > settings.xml any longer. Why ? Because the <mirror> element replaces them > all because maven-proxy handles everything from the URL > "http://NUCLEUS:9999/repository/"; (which is the actual purpose of a proxy). > So for what I've understood, you don't need to activate any extra > repository definition profile when you're using maven-proxy. > Am I wrong? > Maybe "central" is a repository for which snapshots are not activated by > default, and therefore when setting the mirror of "central" to maven-proxy, > it does not handle them?
This bit is still a work in progress. The mirror entry will only mirror artifacts from the repository with the same id as specified in the mirrorOf tag. Internal repositories are not deployed to "central" and therefore maven will not contact maven-proxy, even though I have configured maven-proxy to allow mirroring of the internal repositories. Maven will contact all repositories defined in settings.xml, in the order the are declared, looking for an artifact. So although it is not proxied maven can still locate the artifacts. Not proxying internal repositories isn't a big issue anyway. However from a discussion on the list it became clear that putting repository definitions in settings.xml is not ideal because 1) all developers need to update settings.xml to include the repositories 2) the pom should have authorative information about where dependency artifacts are located. I am still fiddling with this so I have not updated the document yet. So far, I have removed the profiles and activeProfiles section from settings.xml and placed the repository definitions into the repositories section of pom.xml. More will come later. > As for the SNAPSHOT unique version, I put it to "false" because I don't > want to have my snapshot repository getting bigger and bigger too fast. I > know Maven knows well how to handle snapshots when unique version is > activated, but I just want to save space. Fair enough. One other thing I need to add the document, is that I believe that no developer should be issuing the deploy command. This should be happening as part of continuous integration in nightly builds. So your snapshot repository size will be growing 365 times a year at worst. Hopefully some artifacts are being promoted out of snapshot faster than that. Barrie. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
