[
https://issues.apache.org/jira/browse/SLING-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625790#comment-14625790
]
Carsten Ziegeler edited comment on SLING-4879 at 7/14/15 4:25 AM:
------------------------------------------------------------------
While I see the reason behind this, I think the prov model should really be
independent from any build tool. Therefore I think the attached model should
contain the proper values for the variables (= the values from the pom). This
is not exactly the effective model
was (Author: cziegeler):
While I see the reason behind this, I think the prov model should really be
independent from any build tool. Therefore I think attachEffectiveModel=true
should be the default
> Slingstart Maven Plugin: Allow to read variables from POM
> ---------------------------------------------------------
>
> Key: SLING-4879
> URL: https://issues.apache.org/jira/browse/SLING-4879
> Project: Sling
> Issue Type: New Feature
> Components: Maven Plugins and Archetypes
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Fix For: Slingstart Maven Plugin 1.3.0
>
>
> by default provisioning variables can only be resolved by a variables section
> defined inside the provisioning file.
> if processed by the slingstart maven plugin it should be optionally possible
> to reference variables defined within the pom from which the plugin is
> executed. additionally it should be possible to attach an resolved (effective
> model) with those variables replaced when storing it as artifact.
> this is useful if the same property is required within the POM and the
> provisioning file and avoids haven to define and maintain it in two locations.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)