-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi,
I don't think this is currently possible; I would investigate using the release plugin though, as this ensures that versions are always incremented. Cheers, Johan Leder, Leslie (NSN - DE/Greifswald) wrote: > Hello, > assume there is a module A already deployed in version 1.0. Now somebody > changed the code of module A but forgot to increment the version so it > still is 1.0. > So the second version of component A is definitely not ok. But how can I > protect the correct version 1.0 of component A than? The way it works I > know is that the deploy plugin would just overwrite the correct artifact > by the newer but incorrect one. Is this really ok. This would double me > fault score to two. Now I haven't only an attempted version 1.1 but I > also haven't a real 1.0 anymore. > Is there any chance to let Maven2 check if the artifact that is > currently to be deployed differs in size and/or checksum to an already > deployed artifact in the target repository with exactly the same Maven > coordinates (groupId, artifactId, classifier, version, type). > > Thanks, > Leslie > - -- you too? -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHHyst1Tv8wj7aQ34RApX8AKCPYxQQDllYI/h2+Z+39sf9qYGVJgCcCuv4 qAqtVt8fYksX8/3dKil6Rks= =AgME -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
