You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by "Leder, Leslie (NSN - DE/Greifswald)" <le...@nsn.com> on 2007/10/24 12:50:16 UTC
Protection of Already Deploy Artifacts
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
RE: RE: Protection of Already Deploy Artifacts
Posted by "Leder, Leslie (NSN - DE/Greifswald)" <le...@nsn.com>.
I know this one. But for that I would need to change a lot in the SVN
structure which is currently standard conform. Probably this is a fault.
But at the end it is somehow like saying: Don't deal with the fault but
uses this tool that prevents you from making this fault.
There is always somebody in the project who does it in the wrong way.
And than there is a hidden fault which could be there for quite a while
until discovery.
-----Original Message-----
From: ext Nicole Lacoste [mailto:niki.lacoste@gmail.com]
Sent: Wednesday, October 24, 2007 2:21 PM
To: Maven Users List
Subject: Re: Protection of Already Deploy Artifacts
You might want to look into cutting a real release. You only have your
artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release
plugin to cut release in non snapshot version (1.0). The release
prepare
goal creates the 1.0 version and tags the source code in your scm. You
then
create the 1.0 version using the perform goal. You can repeat the
perform
goal as many times as you like, which means even if someone deletes 1.0
or
corrupts it some other way you can always re-perform the release.
Niki
On 24/10/2007, Olivier Dehon <od...@gmail.com> wrote:
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: RE: Protection of Already Deploy Artifacts
Posted by "Leder, Leslie (NSN - DE/Greifswald)" <le...@nsn.com>.
This is at least a prospect. I thought somebody else should also have
this problem.
Thank you,
Leslie
-----Original Message-----
From: ext Brian E. Fox [mailto:brianf@reply.infinity.nu]
Sent: Wednesday, October 24, 2007 2:27 PM
To: Maven Users List
Subject: RE: Protection of Already Deploy Artifacts
There is work occurring on the deploy plugin to not overwrite existing
release artifacts by default.
-----Original Message-----
From: Nicole Lacoste [mailto:niki.lacoste@gmail.com]
Sent: Wednesday, October 24, 2007 8:21 AM
To: Maven Users List
Subject: Re: Protection of Already Deploy Artifacts
You might want to look into cutting a real release. You only have your
artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release
plugin to cut release in non snapshot version (1.0). The release
prepare
goal creates the 1.0 version and tags the source code in your scm. You
then
create the 1.0 version using the perform goal. You can repeat the
perform
goal as many times as you like, which means even if someone deletes 1.0
or
corrupts it some other way you can always re-perform the release.
Niki
On 24/10/2007, Olivier Dehon <od...@gmail.com> wrote:
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: Protection of Already Deploy Artifacts
Posted by "Brian E. Fox" <br...@reply.infinity.nu>.
There is work occurring on the deploy plugin to not overwrite existing
release artifacts by default.
-----Original Message-----
From: Nicole Lacoste [mailto:niki.lacoste@gmail.com]
Sent: Wednesday, October 24, 2007 8:21 AM
To: Maven Users List
Subject: Re: Protection of Already Deploy Artifacts
You might want to look into cutting a real release. You only have your
artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release
plugin to cut release in non snapshot version (1.0). The release
prepare
goal creates the 1.0 version and tags the source code in your scm. You
then
create the 1.0 version using the perform goal. You can repeat the
perform
goal as many times as you like, which means even if someone deletes 1.0
or
corrupts it some other way you can always re-perform the release.
Niki
On 24/10/2007, Olivier Dehon <od...@gmail.com> wrote:
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Protection of Already Deploy Artifacts
Posted by Nicole Lacoste <ni...@gmail.com>.
You might want to look into cutting a real release. You only have your
artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release
plugin to cut release in non snapshot version (1.0). The release prepare
goal creates the 1.0 version and tags the source code in your scm. You then
create the 1.0 version using the perform goal. You can repeat the perform
goal as many times as you like, which means even if someone deletes 1.0 or
corrupts it some other way you can always re-perform the release.
Niki
On 24/10/2007, Olivier Dehon <od...@gmail.com> wrote:
> 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: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Re: Protection of Already Deploy Artifacts
Posted by "Leder, Leslie (NSN - DE/Greifswald)" <le...@nsn.com>.
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:odndev@gmail.com]
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Protection of Already Deploy Artifacts
Posted by Olivier Dehon <od...@gmail.com>.
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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Protection of Already Deploy Artifacts
Posted by Johan Lindquist <jo...@kawoo.co.uk>.
-----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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org