[MRM-964] Method isVersion() for validating an uploaded artifact version is open to criticism

• Type: Wish
• Status: Closed
• Priority: Critical
• Resolution: Duplicate
• Affects Version/s: 1.1.2
• Component/s: Web Interface
• Environment: Client: Windows XP SP3, Firefox 3.0.3; Server: Linux Red Hat AS 4.0
• Assignee: Unassigned
• Reporter: Vincent Thévenin
• Created: 30/Sep/08 11:23
• Updated: 12/Sep/11 11:52
• Resolved: 12/Sep/11 11:52

Description

When uploading an artifact, a validation is made against the 'version' field.
The validation occurs in file $SRC/archiva-modules/archiva-base/archiva-common/src/main/java/org/apache/maven/archiva/common/utils/VersionUtil.java.

I think such a validation algorithm can be discussed, as it does not let the user free to use its own versioning system. Actually, Maven itself does not seem to restrict the string pattern for the version of an artifact (even if the version ranging may not work), so why restricting it at Archiva level?
There are cases where you cannot comply with imposed validation method, and where the change of the version system is not permitted for various reasons. The result is you cannot install the artifact using Archiva.

Issue Links

• duplicates: MRM-929 upload page does not allow certain characters in version string
• is related to: MRM-1172 Invalid version validation error when uploading a jar with a four-part version number
• relates to: MRM-837 Cannot download SNAPSHOT version