[
https://issues.jboss.org/browse/TEIID-3462?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3462:
---------------------------------------
Change the version field to a string rather than an integer, and
allow for the break in backwards compatibility.
While logically straight-forward as I work through it this is a massive change affecting
60+ classes and will break more apis than I had anticipated.
An alternative would be to use a property / file name to indicate the semantic version and
to start by simply deprecating the old version field and using the vdb name to convey the
fully versioned name when appropriate.
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)