[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (TOSCA-134) CLOSE - CSD02 - Define TOSCA version type based upon Apache Maven versioning
[ https://issues.oasis-open.org/browse/TOSCA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matthew Rutkowski updated TOSCA-134: ------------------------------------- Summary: CLOSE - CSD02 - Define TOSCA version type based upon Apache Maven versioning (was: CSD02 - Define TOSCA version type based upon Apache Maven versioning) > CLOSE - CSD02 - Define TOSCA version type based upon Apache Maven versioning > ---------------------------------------------------------------------------- > > Key: TOSCA-134 > URL: https://issues.oasis-open.org/browse/TOSCA-134 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: New Feature > Components: Profile-YAML > Affects Versions: CSD2 > Reporter: Matthew Rutkowski > Assignee: Matthew Rutkowski > Fix For: CSD2 > > > Describe a recommended way for creators of TOSCA templates/types to include normative and comparable version strings based upon Apache Maven methodology (strings). > See: http://books.sonatype.com/mvnref-book/reference/pom-relationships-sect-pom-syntax.html > Which is the best prose i could find on the subject. All Apache docs are class/method references which provide no examples or discussion of methodology. > Derek provided this link as well: > http://maven.apache.org/enforcer/enforcer-rules/versionRanges.html -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]