mvn deploy:deploy-file fails for 3rd party artifact

I'm trying to deploy a 3rd party jar file to Archiva 1.1.3 using the following: $mvn -e deploy:deploy-file -DgroupId=jsr -DartifactId=jsr-305 -Dversion=0.1-SNAPSHOT -Dpackaging=jar -Dfile=ri-0.1-SNAPSHOT.jar -Durl= http://IPADDR/archiva/repository/snapshots -DrepositoryId=snapshots It gives me ba

errors "Unable to find project model" for certain snapshots

Currently we get the following error in Archiva, when clicking certain snapshot-versions: Unable to find project model for [mygroup:uicomponents:0.0.12-20081218.131304-11]. Could it be caused by the automatic repository purge? Anybody had the same error? -- View this message in context: http:/

Re: Uploading POM

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

Re: Uploading POM

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

Re: Uploading POM

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

Lars Weber ist außer Haus.

Ich werde ab 17.01.2009 nicht im Büro sein. Ich kehre zurück am 02.02.2009. In der Zeit meiner Abwesenheit organisiert Helmut Braun meine Vertretung. Sie erreichen Ihn unter helmut.br...@procon-it.de der Telefonisch über +49 89 451 39 -0.

Uploading POM

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

Re: Purge is not working

Hi Deng, yes, sorry, I meant Continuum (1.2.2). The purge in Archiva is working. Maria Odea Ching-5 wrote: > > Hi Marc, > > On Mon, Jan 19, 2009 at 6:06 PM, Marc Lustig wrote: > >> >> I configured the repo purge: >> Repository Days Older Retention Count Delete All >> De

Re: Purge is not working

Hi Marc, On Mon, Jan 19, 2009 at 6:06 PM, Marc Lustig wrote: > > I configured the repo purge: > Repository Days Older Retention Count Delete All > Delete Released > Snapshots ScheduleDefault Enabled Description > CI08 Repository 100 2

Purge is not working

I configured the repo purge: Repository Days Older Retention Count Delete All Delete Released Snapshots ScheduleDefault Enabled Description CI08 Repository 100 2 false trueHIGH_NOON true