[
https://issues.apache.org/jira/browse/MRM-1967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16292146#comment-16292146
]
Pascal Jacob commented on MRM-1967:
-----------------------------------
I think we are getting close now. Problem could be in de POM file. To be
honest, this is our first attempt using an artifact repository like Archiva. So
not all functions are 100% clear to us on how to use them.
We are using following Maven command from within Jenkins to upload the artifact:
{code:java}
mvn deploy:deploy-file -Dfile=globis-solutions.rar
-DpomFile=globis-solutions.xml -DrepositoryId=GO10
-Durl=http://192.168.73.235:8060/repository/GO10 -DupdateReleaseInfo=true
{code}
We have added the -DupdateReleaseInfo parameter, because without it, following
API call did not always return the latest version of an artifact:
{code:java}
http://192.168.73.235:8060/restServices/archivaServices/searchService/artifact?g=10.3.12&a=globis-solutions&v=LATEST&p=rar
{code}
I have also attached the POM file to the issue.
> Purge snapshot repository
> -------------------------
>
> Key: MRM-1967
> URL: https://issues.apache.org/jira/browse/MRM-1967
> Project: Archiva
> Issue Type: Bug
> Components: repository scanning
> Affects Versions: 2.2.3
> Reporter: Pascal Jacob
> Assignee: Martin Stockhammer
> Attachments: Screen Shot 2017-11-29 at 12.48.11.png, archiva.xml,
> artifact-listing.txt, globis-solutions-10.3.12-1.pom.xml
>
>
> Hello,
> I have a snapshot repository with following settings:
> - cron = 0 0 * * * ?
> - days older = 0
> - retention count = 1
> - snapshots = true
> - scanned = true
> - delete released snapshots = true
> Artifact filetype = rar
> Repository scanning consumers:
> - repository-purge = true
> But nothing is purged. Nothing is cleaned up. Not even when starting
> directory indexing manually (UI).
> Any ideas what could be wrong?
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
