Hi Wayne, I got them to "force" to update to the latest remote snapshot using "mvn -U …", which I assume is the maven way?
My next questions is: inside the plugin code, how can it know for a given artifact that it has been updated from remote since the last time the plugin ran? It seems like the download occurs before the plugin mojo[s] are invoked, so as far as the plugin is concerned, it "appears" to originate from the local repository. There is code that is supposed to unpack the packages and do things with them to prep for some platform-specific build steps, and it's relatively expensive code that should only run when a new version or an updated snapshot was actually downloaded from a remote repository. What is happening now is the new snapshot is downloaded when "-U" is on the command line call, but the unpack/config code is not invoked because as far as it's concerned, it has what it needs because (for example) it already unpacked and configured the stuff for 3.0.0-SNAPSHOT. In case it makes a difference, some of these artifacts are plugin dependencies, while some are project dependencies. Thanks for all your assistance, Patrick On Mar 18, 2013, at 4:08 PM, Wayne Fay <[email protected]> wrote: >> Sure! It is Sonatype Nexus. > > Can you (easily) construct a test case where you push a snapshot of > something in using just the GAV (no C) and then pull it back it with > your plugin code, then rinse and repeat a few times to confirm it > either works or fails *without* any classifiers? > > Then you should be in good shape to run a similar test with the only > difference being the classifier is added back. > > Wayne > > --------------------------------------------------------------------- > 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]
