I think you are trying to control dependencies and not plugins right? So in order to do that, you need two different repositores. One for dependencies and one for plugin. Control access to the dependency one and allow free access to the plugin one.
On 9/16/06, Andreas Guther <[EMAIL PROTECTED]> wrote:
Hi, I am struggling with the question on how to maintain a controlled internal repository with Maven 2. We want to have full control over the downloaded dependencies and configured Maven to use as central repository our internal repository server. With this configuration no external repository is used. In my settings.xml file I have configured Ibiblio as external repository server and activate the profile whenever I have to use components with dependencies that are not in our internal repository. The problem I have is that getting the internal/central repository updated with the new dependencies is rather a tedious and time intensive task, especially if for example a maven plug-in is added that comes with lots of transient dependencies. My question is: Ho do other teams deal with that problem? Are there tools that list differences between two different repositories (local and internal)? I used Maven Archiva as proxy repository but that does not give us the control over what gets added to the repository. Thanks in advance for any hint and suggestion. Andreas --------------------------------------------------------------------- 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]
