Then why does the console report it checking for snapshot updates at the three
repositories? Is there a way to force it to look for snapshot updates? I don't
like the unique version idea as it seems more clumsy.
Don
Wendy Smoak wrote:
On 7/19/06, Don Brown <[EMAIL PROTECTED]> wrote:
Yes, just make the change to XWork and assume that CruiseControl will
publish it
correctly. We have noticed that Maven isn't automatically pulling
down the
latest snapshot, for some reason, so everyone else will probably need
to nuke
their cached artifact. (I fail to understand the whole point of a
snapshot if
maven won't check for the latest version, but oh well)
Maven 2.0.4 doesn't retrieve updated snapshots unless you deploy them
with timestamped filenames. There's some discussion on [EMAIL PROTECTED],
apparently it wasn't working quite right and the functionality was
removed for further work.
I don't see it in the xwork pom, but if you're deploying with Maven 2,
somewhere the <snapshotRepository> must be defined with
<uniqueVersion>false</uniqueVersion>. If you take that out, (or set
it to true, which is the default,) it will start working... but if
you're deploying snapshots every hour, a cron job to delete old ones
would be a good idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
