I thought about this also. But this is where story becomes more complicated. Actualy the module is part of a multi-module project. As long as the code does not change the result hopefully will also not change. Repeated build and deployment in the context of an multi-module project is fine so far als long as code and version change consistently. But this is a bit error prone. It's quite easy to forget to update one out of many modules versions.
for example: my project has module A-1.0 and B-1.0 without dependencies step1: deploy A-1.0, B-1.0 step2: change B-1.0 to B-1.1 and keep A-1.0 unchanged step3: deploy A-1.0 (again but ok), B-1.1 setp4: change B-1.1 to B-1.2 and modify A-1.0 but forget to update the version step5: deploy A-1.0 (again but this is not ok because the intended A-1.1 is currupt), B-1.2 So I could not protect the artifact by just make it readonly. Because in case it is exactly the same it should be redeployed or skipped. In case it is different but has identical coordinats it should not be deployed. Leslie -----Ursprüngliche Nachricht----- Von: ext Olivier Dehon [mailto:[EMAIL PROTECTED] Gesendet: Wednesday, October 24, 2007 2:05 PM An: Maven Users List Betreff: Re: Protection of Already Deploy Artifacts You can set the files to read-only in the file system. -Olivier 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 > > --------------------------------------------------------------------- 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]
