We have a local repo manager and it still takes a fixed amount of time per 
artifact.  It would take a few minutes to totally rebuild a local repo as we 
have a fair number (hundreds) of artifacts, and Maven itself requires a bunch 
of plugins just to get started.  Granted I could just delete my group from the 
local repo tree to speed things up, but I don't understand why we need to do 
this when the SNAPSHOT notion seemed to work just fine for us.  The SNAPSHOT 
version was useful and I'm not sure why it was taken out in M3.

-----Original Message-----
From: Brian Fox [mailto:[email protected]]
Sent: Friday, August 06, 2010 11:42 AM
To: Maven Users List
Subject: Re: Problem with uniqueVersion=false in 3.0 beta1

No, but with a repo manager, it's pretty quick to wipe the local and
refetch everything cleanly from the local network.

On Fri, Aug 6, 2010 at 10:31 AM, Adam Krieg <[email protected]> wrote:
> Is the local repository smart enough to clear out the old snapshots?  I'm 
> worried about tons of irrelevant artifacts.
>
> -----Original Message-----
> From: Stephen Connolly [mailto:[email protected]]
> Sent: Thursday, July 15, 2010 4:00 PM
> To: Maven Users List
> Subject: Re: Problem with uniqueVersion=false in 3.0 beta1
>
> You recall correctly, uniqueSnapshots will always be true for M3
> irrespective of what you try to set it to
>
> -Stephen
>
> P.S. I don't understand exactly why... I think it has something to do with
> Repository managers being sufficiently good that they can reclaim the disk
> space for you so the non-unique is no longer required.
>
> On 15 July 2010 20:28, Anders Hammar <[email protected]> wrote:
>
>> IIRC Maven 3 only supports unique versioned snapshots (currently). There
>> was
>> some discussion easlier here on the mailing list regarding that. Search
>> some
>> archive for more info.
>>
>> /Anders
>>
>> On Thu, Jul 15, 2010 at 21:24, Adam Krieg <[email protected]>
>> wrote:
>>
>> > I'm trying to configure Maven to not create unique snapshots.
>> >
>> > When using the following settings in Maven 2.2.1, this works:
>> >
>> >        <snapshotRepository>
>> >            <uniqueVersion>false</uniqueVersion>
>> > ....
>> >
>> >
>> > However when I run with Maven 3.0 beta 1, I get autogenerated numbers
>> > appended, as if uniqueVersion was true.
>> >
>> >
>> > Is anyone else seeing this behavior?
>> >
>> > Disclaimer: http://pragmatrading.com/disclaimer.html
>> >
>>
>
> Disclaimer: http://pragmatrading.com/disclaimer.html
>
> ---------------------------------------------------------------------
> 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]


Disclaimer: http://pragmatrading.com/disclaimer.html

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to