[
http://jira.codehaus.org/browse/MRM-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174289#action_174289
]
jan ancajas commented on MRM-1172:
----------------------------------
>From what I've traced this has something to do with the version algorithm
>implementation :
1. tokenize the string using "-" (dash) as the separator
2. checks if each token matches the regex pattern (see below)
3. the token ratio between "matching tokens" and "all tokens" must be 75% or
more.
>From the example it's only 50%.
We can loosen the rule a bit to return true if the first token is a matching
token. thoughts on this ?
{noformat}
"([0-9][_.0-9a-z]*)",
"(snapshot)",
"(g?[_.0-9ab]*(pre|rc|g|m)[_.0-9]*)",
"(dev[_.0-9]*)",
"(alpha[_.0-9]*)",
"(beta[_.0-9]*)",
"(rc[_.0-9]*)",
"(debug[_.0-9]*)",
"(unofficial[_.0-9]*)",
"(current)",
"(latest)",
"(fcs)",
"(release[_.0-9]*)",
"(nightly)",
"(final)",
"(incubating)",
"(incubator)",
"([ab][_.0-9]+)"
{noformat}
> Invalid version validation error when uploading a jar with a four-part
> version number
> -------------------------------------------------------------------------------------
>
> Key: MRM-1172
> URL: http://jira.codehaus.org/browse/MRM-1172
> Project: Archiva
> Issue Type: Bug
> Components: web application
> Affects Versions: 1.2.1
> Environment: Archiva 1.2.1-SNAPSHOT trunk r761865
> Reporter: Wendy Smoak
> Priority: Minor
> Fix For: 1.2.1
>
>
> Archiva will not allow you to upload an artifact with a version number in the
> format 2.5-r123456-proj-1.2.3
> We use this version number format to do internal releases of third-party
> artifacts.
> Deploying from the command line works, but the artifact upload form in
> Archiva will not accept this version number and displays "Invalid version".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
