I would aggregate all of your local plugins into a local-only pom.xml which would identify your local repository as your 'primary repository' when using the local-only pom you would always identify 2.8.1 as the only maven-javadoc-plugin stored in local repository the other poms will reference the 'normal' repositories from maven settings.xml which will of course reference the 2.5 maven-javadoc-plugin
http://maven.apache.org/guides/introduction/introduction-to-repositories.html Martin Gainty ______________________________________________ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. > Subject: Override plugin dependencies? > From: [email protected] > Date: Mon, 20 Aug 2012 18:50:16 -0600 > To: [email protected] > > I have a couple of quick questions about plugins and their dependencies. I > am on a private network so it is sometimes difficult to get a plugin and all > it's dependencies. > > 1. I am trying to use the maven-release-plugin and during the deploy phase > it is looking for the maven-javadoc-plugin version 2.5. I have version 2.8.1 > in my private archiva repository. Is there anyway I can specify when using > the release plugin to use a different version for one of its dependencies. > > 2. I do not think #1 is possible for a few reasons. As such is there a good > way to download a plugin and all of its dependencies so that I can bring them > over to a private repository? I think the problem here is that different > dependencies are pulled during different phases of the build, so unless I > actually run the plugin I am not sure I can get all the dependencies. Any > thoughts? > > Thanks, > Billy > > Sent from my iPhone > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
