Billy according to http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html Requires dependency resolution of artifacts in scope: test.
did you specifically configure go-offline to include compile scope (via includeScope)? http://maven.apache.org/plugins/maven-dependency-plugin/go-offline-mojo.html#includeScope Martin ______________________________________________ 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. > From: [email protected] > Date: Tue, 21 Aug 2012 09:20:37 -0600 > Subject: Re: Override plugin dependencies? > To: [email protected] > > Anders, > > I agree with you comment about internet access. Unfortunately I will > never have access to the internet from my workstation. This has made > maven extremely painful to work with, but something I have to deal > with. > > As for your solution I cannot get it to work. In my main pom I have: > <build> > <pluginManagement> > <plugins> > <plugin> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.8.1</version> > ..... > > > > > When I try to use the release:perform goal I get the following error: > > Error building POM (may not be this projects POM) > > Project ID: org.apache.maven.plugins:maven-javadoc-plugin > > Reason: POM 'org.apache.maven.plugins:maven-javadoc-plugin' not found > in repository: Unable to download the artifact from any repository > org.apache.maven.plugins:maven-javadoc-plugin:pom:2.5 > > > So this error is not telling me anything I don't already know, > maven-javadoc-plugin version 2.5 is not in my repository, I only have > version 2.8.1. But adding version 2.8.1 to my plugin management > section did not work as the release-plugin has a dependency that has a > dependency on version 2.5. > > Sure I can pull version 2.5 back to my internal repo, but if I can > control the version of a plugin that maven would use throughout its > build (even if another pom says use a different version) that would > help. > > I also tried to create a pom with maven-release-plugin defined then: > mvn dependency:go-offline > > That pulled some of the dependencies but not all. I.E. that did not > pull the maven-javadoc-plugin > > Any more ideas? > > Thanks for all the help thus far. > Billy > > > On Mon, Aug 20, 2012 at 11:57 PM, Anders Hammar <[email protected]> wrote: > > Just ignore Martin's mail. It doesn't make any sense to me either. > > > > To answer your questions, I'll start with #2 first: > > > > The best solution to this problem is to get a repo manager (archiva in > > your case) that has Internet access. It will be VERY difficult for you > > to work with Maven unless you do this. Trust me, I've tried! > > > > And then #1: > > > > What you need to do is to define the version of the plugins you want > > to use in the pluginManagement section. The best solution to handle > > this is to do this in a parent pom which all your projects inherit > > from. This will ensure that you'll use that version you want, and it > > will also ensure that the same version is always used (which is not > > the case when you don't pin down the version, it could then change > > when new versions are released or when you upgrade Maven depending on > > what plugin we're talking about). > > > > > > > > On Tue, Aug 21, 2012 at 3:21 AM, Billy Newman <[email protected]> wrote: > >> This is very confusing to me. I have a remote repository (Archiva) where > >> we store all the plugins we bring in. This includes version 2.3.2 of the > >> release plugin. When I use the 2.3.2 release plugin it asks for 2.5 of the > >> javadoc plugin which I do not have in my internal remote repository. > >> > >> Sent from my iPhone > >> > >> On Aug 20, 2012, at 7:13 PM, Martin Gainty <[email protected]> wrote: > >> > >>> > >>> 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] > >>>> > >>> > >> > >> --------------------------------------------------------------------- > >> 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] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] >
