When you build foo-1.0.3-SNAPSHOT, the build treats that version as is until you reach the deploy stage.
At deploy, the deploy plugin gives it the timestamp... so the timestamp is only available when you get to the deploy phase (i.e. after deploy you'd be able to get foo-1.0.3-20081104.143523-57) Unfortunately for you, you are looking for the value before it exists... now if this is for a separate module, then you might stand a chance -Stephen 2008/11/7 Paul <[EMAIL PROTECTED]> > I'm only changing the subject as I understand that it was completely > unclear :) > > Hello, > > Since I've setup a CI server at my java shop we have snapshots autodeployed > to > our internal repo. > > This is cool :) But as a side effect I see some artifacts being used in > builds > with snapshots versions (like foo-1.0.3-20081104.143523-57.jar). This is > expected. > > Regarding this I have one question. > > We use a home grown maven plugin that plays with project dependencies and > detects if a dependency has a particular classifier attached. To do this it > tries to download the eventually attached artifact for all dependencies of > the project. Thanks to full featured maven repositories and good naming > convention, we reduced the internal download request number a lot and the > external download request number down to zero (using black/white listing). > > My mojo gets the snapshot dependencies versions as X.X.X-SNAPSHOT and tries > to > download X.X.X-SNAPSHOT-classifier. It has happen that a snapshot version > had > the attached artifact but not another version of the same snapshot and my > plugin fetched a wrong version of it. > > It's a little bit hard to explain, if you don't get the idea I can > reformulate :) > > So, I would like to know how to get the "snapshot version" of a snapshot > dependency in my mojo so I can use a precise version to trigger the > download > try. > > Any help appreciated. > > Paul > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
