And at times you can use the '-U' option to force an update check for
dependencies.
Rahul
Simon Kitching wrote:
---- Stephen Connolly <[EMAIL PROTECTED]> schrieb:
Redeploying a non-SNAPSHOT version is a _bad thing_ as Maven will not
re-download it.
Absolutely. Never overwrite an existing deployed file except when it has
SNAPSHOT in the version.
Builds should be repeatable, ie you should be able to compile something today,
then compile it again next week and get the same result. This means that stuff
deployed to a repository should never change.
The only exception is SNAPSHOT versions; when a project depends on one of these, then it is explicitly acknowledging that repeatable builds are not possible.
One of the things the release plugin does is check that there are no SNAPSHOT
dependencies anywere; if there are then it refuses to continue with the release
process as the release is not repeatable. Of course using the release plugin is
not mandatory, but that particular check is a very good idea.
And because Maven assumes people never overwrite non-snapshot files, it never bothers to check for newer
ones. Only with SNAPSHOTs does maven look for newer versions, on an "every time", "daily"
or "weekly" basis as configured.
Regards,
Simon
---------------------------------------------------------------------
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]
