[
https://issues.apache.org/jira/browse/SLING-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625843#comment-14625843
]
Stefan Seifert commented on SLING-4880:
---------------------------------------
the provisioning model is extended by an "ArtifactVersionResolver" which is
optional. it only steps in when in the provisioning model no version is defined
for an artifact (which defaults to "LATEST"). if the ArtifactVersionResolver
does not resolve a version it is still LATEST.
the slingstart file generated when this feature that is attached to the
artifact does by default not insert the artifact versions, because by default
the "raw model" is attached. but if the new property "attachEffectiveModel"
which was introduced in context of SLING-4879 is set to true the effective
model is attached which resolves both variables and pom versions. then the
resulting model then can indeed used by any build tool and they do not have to
know anything about POM dependencies or properties.
> Slingstart Maven Plugin: Allow to get artifact versions from POM
> ----------------------------------------------------------------
>
> Key: SLING-4880
> URL: https://issues.apache.org/jira/browse/SLING-4880
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes, Tooling
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: Sling Provisioning Model 1.3.0, Slingstart Maven Plugin
> 1.3.0
>
>
> Currently it is possible to define an exact artifact version in a
> provisioning file, or define now version, "LATEST" is used in this case
> automatically.
> When no explicit version is defined in the provisioning file it should be
> optionally possible to use the version defined in the dependency or
> dependencyManagement section of the maven projects POM file.
> This is especially useful if the dependency is there defined anyway and
> should not have to be set and maintained on two locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
