[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-134) WD02 - Define TOSCA version type based upon Apache Maven versioning
[ http://tools.oasis-open.org/issues/browse/TOSCA-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36676#action_36676 ] Luc Boutier commented on TOSCA-134: ----------------------------------- See also: http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution#DependencyMediationandConflictResolution-DependencyVersionRanges > WD02 - Define TOSCA version type based upon Apache Maven versioning > ------------------------------------------------------------------- > > Key: TOSCA-134 > URL: http://tools.oasis-open.org/issues/browse/TOSCA-134 > Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC > Issue Type: New Feature > Components: Profile-YAML > Affects Versions: CSD1 > Reporter: Matthew Rutkowski > Assignee: Derek Palma > Fix For: CSD1 > > > 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 is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]