afaik, the deploy plugin will not overwrite a version that has
previously been deployed
certainly, the major repository managers do not allow re-deployment
the only issue you may have is what happens when you loose your
repository and have to re-construct from scm... the hard rule you
describe would prevent that recovery process
Sent from my iPod
On 21 Dec 2008, at 21:28, konkere <[email protected]> wrote:
the feature i'm interested in is to be able to prohibit a developer to
install/deploy/release an updated artifact under the same version
that is
already in the repository.
our previous release management system was build around the concept of
complete uniqueness of a version, which meant that if a project is
in the
repository under a certain version, then the only way to release this
project again is to change the version. it wasn't possible to
overwrite the
artifact using one of the existing versions.
so i wonder, if there's a similar way to organize releases in maven?
docs
for release and deploy plugins don't say anything about this
particular
functionality.
--
View this message in context:
http://www.nabble.com/possibility-to-control-an-artifact-version-when-installing-deploying-releasing--tp21119401p21119401.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
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]
