Affects Version/s: 1.1.2
Fix Version/s: None
Component/s: Web Interface
Environment:Client: Windows XP SP3, Firefox 3.0.3
Server: Linux Red Hat AS 4.0
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.
|Workflow||jira [ 12945665 ]||Default workflow, editable Closed status [ 12982906 ]|
|Project Import||Sun Apr 05 21:01:51 UTC 2015 [ 1428267711911 ]|
|Workflow||jira [ 12707789 ]||Default workflow, editable Closed status [ 12737303 ]|
|Project Import||Sun Apr 05 08:30:08 UTC 2015 [ 1428222608952 ]|
|Resolution||Duplicate [ 3 ]|
|Status||Open [ 1 ]||Closed [ 6 ]|
|Fix Version/s||Backlog [ 13571 ]|
|Fix Version/s||1.x [ 13571 ]|