maven-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Brian E. Fox" <bri...@reply.infinity.nu>
Subject RE: [jira] Created: (MARTIFACT-6) The deployer should detect previous deployments of the same version and die if that's the case.
Date Tue, 06 Nov 2007 07:20:20 GMT
I don't completely agree that non unique should be essentially killed.
Unless you are letting people pin to a specific snapshot instance,
(which IMO is much worse) there are no problems using the non unique
stuff. We switched to it because we were using up over 300gb / week from
our continuous integration builds. 

I think worse problems crop up when people start hand picking their
snapshot versions. This might be ok for OSS but internal commercial, if
the latest isn't working, I want to know it and I want it fixed asap.

--Brian

-----Original Message-----
From: Jason van Zyl [mailto:jason@maven.org] 
Sent: Tuesday, November 06, 2007 6:42 AM
To: Maven Developers List
Subject: Re: [jira] Created: (MARTIFACT-6) The deployer should detect
previous deployments of the same version and die if that's the case.

They die.

How that non unique stuff creep in should be looked at. As a short  
term convenience for not having to wipe stuff out is far less  
important in that you can hose an entire team. Most people nuke the  
snapshots after a couple weeks but in that period no one can lock down  
to anything and you potentially hose a lot of people.

If we actually get it to work in 2.0.x then some mode for allowing  
that could be added but it's a terrible practice to have non-unique  
snapshots. So it didn't occur to me because I tell people to never use  
that feature unless they enjoy wasting their time figuring how to roll  
back to something stable. It's another "the convenience doesn't out  
weight the dire consequences".

On 5 Nov 07, at 9:26 PM 5 Nov 07, Brett Porter wrote:

> What about non-unique-versioned snapshots?
>
> - Brett
>
> On 06/11/2007, at 4:23 PM, Jason van Zyl (JIRA) wrote:
>
>> The deployer should detect previous deployments of the same version  
>> and die if that's the case.
>>
------------------------------------------------------------------------
-----------------------
>>
>>                 Key: MARTIFACT-6
>>                 URL: http://jira.codehaus.org/browse/MARTIFACT-6
>>             Project: Maven Artifact
>>          Issue Type: Improvement
>>    Affects Versions: 3.0-alpha-1
>>            Reporter: Jason van Zyl
>>
>>
>> We simply have to die because giving people an option is just going  
>> to let them continue with their bad practices. If you let the  
>> redeployment of released binaries then it will happen, and it will  
>> cause problems.
>>
>> -- 
>> This message is automatically generated by JIRA.
>> -
>> If you think it was sent incorrectly contact one of the  
>> administrators: http://jira.codehaus.org/secure/Administrators.jspa
>> -
>> For more information on JIRA, see:
http://www.atlassian.com/software/jira
>>
>>
>
> --
> Brett Porter - brett@apache.org
> Blog: http://www.devzuz.org/blogs/bporter/
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>

Thanks,

Jason

----------------------------------------------------------
Jason van Zyl
Founder,  Apache Maven
jason at sonatype dot com
----------------------------------------------------------




---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org


Mime
View raw message