Github user kevin-canadian commented on the issue:
https://github.com/apache/maven/pull/112
Thanks for the quick reply.
This PR was prompted by a bug we discovered in our production build
environment. When we updated our release artifact version number format to be
<major>.<minor>.<patch>-YYYYMMDD-HHmmss-<build-number>, release artifacts were
erroneously being sent to snapshot repositories, resulting in strange issues in
our Archiva repository.
The reason appears to be that the regex used to identify timestamp-tagged
snapshot version numbers erroneously uses a wildcard "." instead of a literal
"." to match the separator between date and time. This results in our version
format, which uses a "-" as the separator, being incorrectly identified as a
timestamp-tagged snapshot version number instead of a release version number.
For now we just modified our release artifact version number format to
something else. When I find the time I'll create a JIRA issue and a proper
patch for this issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
