Automated Versioning As A Mechanism For Component Software
- 1. Automated Versioning As a Mechanism for Component Software Consistency GuaranteeJaroslav BAUMLDept of Computer ScienceUWB, Pilsen
- 2. ComponentEvolutionComponent updates reflect their evolutionApplication consistency during updatesOne release of componentDependencies to componentsReleases during timeDepencencies to explicit releases of components (specified by version)10/27/20092Bauml: Automated Reliable Versioning
- 3. VersionsVersions are one of the most important thing in component development…Do not believe?10/27/20093Bauml: Automated Reliable Versioning
- 4. VersionsVersions are one of the most important thing in component development…10/27/20094Bauml: Automated Reliable Versioning
- 5. VersionsVersions are one of the most important thing in component development…… because they handle (or describe) component evolutionUnfortunately is also one of the less trackedCommon versioning scheme:major.minor.micro_textualAddons1.4.2_alpha210/27/20095Bauml: Automated Reliable Versioning
- 6. Current use ofversionsemanticsVery often versioning only adhocMarketing purposeSemantic purposeAll incompatible changes <=> majorid++.All backward compatible <=> minor id++.No changes on interface <=> microid++.10/27/20096Bauml: Automated Reliable Versioning
- 7. Semantic VersioningNo tooling, even no methodologyto create semantic versioning.Specifications talk about “compatibility”, but it is too weak.To determine what is and what is not compatible, we can use structuralsubtyping.10/27/20097Bauml: Automated Reliable Versioning
- 8. Subtyping as key solution for semantic versioningCan use Car instead of Vehicle. Car is a subtype of …A compatiblewithB <=>B <: A 10/27/20098Bauml: Automated Reliable VersioningDifference values: NON, MUT, SPE, GEN evaluate at leaves
- 9. combine to root:spe ⊕ gen -> mutmut ⊕ X -> mutnon ⊕ X -> X
- 10. SubtypingExample10/27/20099Bauml: Automated Reliable VersioningRold =majold.minold.micoldRnew = majnew.minnew.micnew
- 11. Subtyping Example (2)Two consecutive revisions, versions: The function Difference (Rold,Rnew) is defined by the rulesin the table.10/27/200910Bauml: Automated Reliable VersioningOLD Logger 1.2.4, wefoundMutation => NEW Logger‘s version = 2.0.0
- 12. Our Implementation for OSGiSimple meta-models Implementation of subtypingJava levelJavaTypes – general project to handle java type system at runtimeBytecode, reflection, …Bundle levelMetadata inspection10/27/200911Bauml: Automated Reliable Versioning
- 13. Validation – Real World BundlesTo provide a basic validation of proposed principle, implemented tool was tested on bundles from Apache Felix archive.10/27/200912
- 14. ConclusionOur methodallows you to ensure component consistencypossible by component type representationas strong as type information allows (semantic changes, dynamic features)“No matter how sophisticated a (versioning) scheme is, it is useless if it is not used by all components universally.”10/27/200913 /18Bauml: Automated Reliable Versioning