>One minor thing, the current proposal uses the Maven coordinates to >describe artifacts. It's using the path part of a maven url, so >basically group id, artifact id, version are separated by a slash. It >seems that the notation of separating these things by a colon is more >common/natural. And we'll probably switch to that.
i always stumbled about this in the current provisioning model as well - afaik this is the most used standard to describe maven artifact coordinates in a single string: https://maven.apache.org/pom.html#Maven_Coordinates that means the following syntax variants are allowed: groupId:artifactId:version groupId:artifactId:packaging:version groupId:artifactId:packaging:classifier:version in the slingstart maven plugin we added support for special maven integration: - including properties from maven pom inside provisioning model - leaving out artifact version from provisioning model and getting it from the pom dependencies is it planned to support something like this in sling feature as well? this was very useful when provision models where declared in context of a maven reactor build with all versions in one place (e.g. central parent pom). otherwise you need to define the versions twice - in the maven poms and in the sling feature/provision model, which is a source for errors. stefan
