[
https://issues.apache.org/jira/browse/SLING-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert reopened SLING-4879:
-----------------------------------
will do.
not so trivial because it would not be good to inject just all properties from
the pom - this would pollute the variables section with loads of maven-specific
properties. i will try to inject only those variables references anywhere
within the model.
> 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)
