[
http://jira.codehaus.org/browse/MRM-1172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=174340#action_174340
]
Wendy Smoak commented on MRM-1172:
----------------------------------
Is there logic somewhere in Maven to decide whether a version number is valid?
Why would Archiva be more strict about this?
I've never had a build fail due to an invalid version number... it may not be
able to find the dependency, and creative version number formats don't work
well with ranges, but not invalid.
> 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
>
> Attachments: MRM-1172.patch
>
>
> 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
