You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@archiva.apache.org by "Guimiot Isabelle (JIRA)" <ji...@codehaus.org> on 2014/09/05 13:48:10 UTC
[jira] (MRM-1846) Regression in 2.0.1 : uniqueVersion false not
supported
[ https://jira.codehaus.org/browse/MRM-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guimiot Isabelle reopened MRM-1846:
-----------------------------------
I really apologize, but in fact, I think the issue isn't completely fixed : I didn't pay enough attention when I said it was ok 2 months ago, shame on me...Now that I deeply test the latest version, I realize it's still not working.
Since 2.1.0, the name of the artifact published really ends with -SNAPSHOT (instead of -null-buildnumber in 2.0.1), which is correct and made me think it was fixed, *but* when I click on it (or try to download it as a dependency from another project), it's still searching an artifact called artifact-null-buildnumber, and I get that kind of message :
Not a valid artifact path in a Maven 2 repository, filename 'myArtifact-2.5.3-null-0.pom' doesn't contain a timestamped version matching snapshot '2.5.3-SNAPSHOT'
I precise that it affects both 2.1.0 and 2.1.1.
I hope you could fix it in 2.1.2 ?
Thanks a lot !
> Regression in 2.0.1 : uniqueVersion false not supported
> -------------------------------------------------------
>
> Key: MRM-1846
> URL: https://jira.codehaus.org/browse/MRM-1846
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 2.0.1
> Environment: Maven 2.2.1
> Reporter: Guimiot Isabelle
> Assignee: Olivier Lamy
> Fix For: 2.1.0
>
>
> When using maven 2.2.1 and defining in the pom a snapshot repo configured with uniqueVersion=false, the artifacts are published as artifact-x.y.z-null-[buildNumber].jar, instead of artifact-x.y.z-SNAPSHOT.jar.
> It used to work fine in 1.3.x and 1.4-M4.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)