Simon Moore wrote:
> This is what is happening to me aswell though I'm getting a few more than
> you ;)
>
> I tried updating my maven install to CVS HEAD yesterday (fresh checkout,
> succesfull bootstrap, all the plugins ;) but I was having a number of
> problems with the site plugin complaining about a missing method (I checked
> the archives which recommended to copy the latest jelly-snapshot into
> maven\lib but that didn't help)
> so today I decided to start afresh and...no goals...
The SNAPSHOTS are to be suspected, because my Maven installation that
was bootstraped yesterday on 10:30 GMT works OK.
Living on the edge, right? :)
This makes me think about an extension to the SNAPSHOTS mechanism that
would allow you to build aganist a set of jars that *were* SNAPSHOTS at
given time. HTTP does not allow one to list contents of a directory, so
it is not possible in the current infrastructure. But if the
snapshot deployment script was modified to append the name of
the uploaded artifact to a file named ${ARTIFACT}-SNAPSHOTS.list the
dependency resolver could download that file, parse it and determine the
name of the file that contains the newest snapshot at that point of
time, or optionaly some other point of time if the user explicity
requested it. This would also make the -SNAPSHOT symlinks in the
repository unnecessary.
R.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
