You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/07/14 09:25:04 UTC
[jira] [Reopened] (SLING-4880) Slingstart Maven Plugin: Allow to
get artifact versions from POM
[ https://issues.apache.org/jira/browse/SLING-4880?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seifert reopened SLING-4880:
-----------------------------------
needs some refactoring along with SLING-4879 to only inject the resolved versions but keep the raw models.
> 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)