When manually including a feature dependency in a template feature file for the features-generate-descriptor goal of the karaf maven plugin in karaf 4.x, is there anyway to get the plugin to automatically generate a semantic version, similar to the way the bnd tool does with the manifest? For example a feature template containing:
<feature>spring</feature> could result in a runtime feature file containing: <feature version="[4.1,5)">spring</feature> for a spring consumer? -- View this message in context: http://karaf.922171.n3.nabble.com/Karaf-Features-generate-descriptor-Goal-Automatic-Semantic-Versioning-tp4046237.html Sent from the Karaf - Dev mailing list archive at Nabble.com.
