You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2015/07/14 06:24:14 UTC

[jira] [Commented] (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:comment-tabpanel&focusedCommentId=14625788#comment-14625788 ] 

Carsten Ziegeler commented on SLING-4880:
-----------------------------------------

While I see the reason behind this, I think the prov model should really be independent from any build tool. I haven't looked at the implementation but I assume that the model artifact that is generated by the project has the versions set - therefore it can be used by any other tool ootb?

> 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)