[
https://issues.apache.org/jira/browse/SLING-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert resolved SLING-4879.
-----------------------------------
Resolution: Fixed
Completed: At revision: 1690898
behavior is changed, this solution is better.
now only one plugin parameter is left:
{code:java}
/**
* If set to true, properties from the Maven POM can be used as variables
in the provisioning files.
* The resolved variables are added to the generated provisioning file, so
other tools using this model
* do not have to resolve them themselves.
*/
@Parameter(defaultValue="false")
protected boolean usePomVariables;
{code}
it is ensured that only those parameters are added to the provisioning file
that are referenced. it is possible to overwrite existing variables that
already existed in the source provisioning file by setting a new value as
property in the POM.
> 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)
