[
https://issues.apache.org/jira/browse/SLING-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-4880.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1690902
refactored along with SLING-4879 to not attach the effective model but only a
model where dependencies from pom are resolved so downstream tooling does not
have to resolve them themselves.
we support two config parameters:
{code:java}
/**
* If set to true, Artifact dependencies from provisioning file without
explicit version are tried
* to be resolved against the dependency versions from the Maven POM.
*/
@Parameter(defaultValue="false")
protected boolean usePomDependencies;
/**
* If set to true, an exception is throws when "usePomDependencies" is set
to true and some
* dependency version could not be resolved in the Maven POM.
*/
@Parameter(defaultValue="false")
protected boolean allowUnresolvedPomDependencies;
{code}
> 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)
