in past I had problems with this "implicit update" on new versions of a plugin and screwed my build. ever since I put the plugin version and if I feel like updating the plugin I change the version. so I also know that everyone who uses my build uses the same plugin version I did and we are all in the same boot - reproducibility.
maven3 warns you about a missing plugin version. regards Kristian On Mon, Aug 16, 2010 at 8:47 PM, C. Benson Manica <[email protected]> wrote: > Ok, well in this case it's merely frustrating, but had we needed to do a > build urgently it sounds like we'd essentially be screwed. How does one > configure Maven to build anyway regardless of whether some plugin happens to > have a more recent update that isn't available from somewhere yet? > Incidentally, my work machine builds the projects correctly, but also > doesn't seem to be downloading the 2.6 plugin (it's nowhere to be found in > my repository). > > On Mon, Aug 16, 2010 at 11:08 AM, Stephen Connolly < > [email protected]> wrote: > >> Not all mirrors may have synced... >> >> I checked from my work machine (which is not configured for fancy proxying >> and from which I did not do the release) and it was downloaded correctly. >> >> Give it 24 hours worst case >> >> On 16 August 2010 16:02, C. Benson Manica <[email protected]> wrote: >> >> > Our projects are configured to download plugins from an Artifactory >> server. >> > Since the 2.6 Surefire plugin was released this morning, nothing is >> > building >> > because the build server can't get the 2.6 plugin from Artifactory. Is >> > Artifactory and/or our projects misconfigured, or is something actually >> > wrong? >> > >> > -- >> > C. Benson Manica >> > [email protected] >> > >> > > > > -- > C. Benson Manica > [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
