[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
Committed the change to use a string version field and tried to consolidate as much
versioning logic on the VDBKey class as possible. The scheme is now:
vdb.1 -> is effectively short hand for vdb version 1.0.0, but we'll display the
version as 1 for backwards compatibly.
.v is no longer needed. The version is just an expanded form -> vdb.1.1.1 will mean
version 1.1.1.
qualifiers are not yet supported.
with rest we expect the url and the war name to use _ instead of . to match the old
behavior.
with odata we'll default to the "1.0.0" version if none is specified.
Add support for semantic versioning of VDBs
-------------------------------------------
Key: TEIID-3462
URL:
https://issues.jboss.org/browse/TEIID-3462
Project: Teiid
Issue Type: Feature Request
Components: Server
Affects Versions: 8.7
Reporter: Marc Shirley
Assignee: Steven Hawkins
Fix For: 9.0
Semantic versioning [1] should be supported in the VDB versioning in order to be able to
easier determine whether there are breaking changes from the client perspective and to
more easily establish a link between client software versions and the VDBs they rely
upon.
[1]
http://semver.org/
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)