This is how I think it works, and the common practice in my opinion:
- Every time you deploy an snapshot version, a version with SNAPSHOT
replaced by the timestamp is created.
- This snapshot is never replaced.
- Archiva can purge snapshots based on age or number of snapshots.
- You declare depende
I thought that for snapshots the behaviour was different...
Will the client still find the latest snapshot or only the 1.0-SNAPSHOT ?
What is the common practice on this? To modify the pom?
2009/1/19 Martin Höller :
> Hi!
>
> On 19 Jan 2009, emerson cargnin wrote:
>> I'm having some problems when
Hi!
On 19 Jan 2009, emerson cargnin wrote:
> I'm having some problems when uploading a POM. When I try to upload a
> second time a snapshot, it will create a timestamp based one like:
> * 1.0-20090119.095642-1/
> * 1.0-20090119.100853-1/
> * 1.0-SNAPSHOT/
>
> These was after the thir
Hi
I'm having some problems when uploading a POM. When I try to upload a
second time a snapshot, it will create a timestamp based one like:
* 1.0-20090119.095642-1/
* 1.0-20090119.100853-1/
* 1.0-SNAPSHOT/
These was after the third time uploading the pom.xml.
I tried to remove phisic
