[
https://issues.apache.org/jira/browse/MRM-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15497200#comment-15497200
]
Martin Stockhammer commented on MRM-1917:
-----------------------------------------
I cannot reproduce the problem. Could you please provide more information:
- How many repositories do you have in your configuration?
- Did you check the permissions of your repository?
- What type of content storage do you use?
- How many versions of your artifact are stored in your repository
- What is the configured cron string of your repository?
[~ganthore]: if you get always the 204, then I think the artifact is not
indexed. Do you find your artifact by the Search form in the Web UI?
> REST API doesn't work the second time with v=LATEST
> ---------------------------------------------------
>
> Key: MRM-1917
> URL: https://issues.apache.org/jira/browse/MRM-1917
> Project: Archiva
> Issue Type: Bug
> Components: rest services
> Affects Versions: 2.2.0
> Reporter: Mohamed
> Priority: Critical
>
> Please find below the URL I use to get the latest version of artifacts. The
> URL is working fine the first time, and when I retry it seems broken nothing
> is received by the browser or by CURL script.
> http://archiva.company.com/restServices/archivaServices/searchService/artifact?g=com.company&a=company-artifact&v=LATEST&p=jar&r=snapshots
>
> We use this API to get the latest version of artifacts it is a main part in
> our infrastructure for continuous delivery.
> Could you please check that? There is no simple manner to handle that ?
> Thnak you
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
