[jira] [Resolved] (SLING-4880) Slingstart Maven Plugin: Allow to get artifact versions from POM

["Stefan Seifert (JIRA)" <ji...@apache.org>]

     [ 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: 1690829  

by default, the current behavior is unchanged. but with a new optional plugin property it is possible to activate the new behavior:

{code:java}
    /**
     * If set to true, Artifact dependencies from provisioning file without explict version are tried 
     * to be resolved against the dependency versions from the Maven POM.
     */
    @Parameter(defaultValue="false")
    protected boolean usePomDependencies;
{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)