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/13 22:46:06 UTC

[jira] [Resolved] (SLING-4879) Slingstart Maven Plugin: Allow to read variables from POM

     [ 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: 1690815  

by default, the current behavior is unchanged. but with two new optional plugin properties it is possible to activate the new behavior:

{code:java}
    /**
     * If set to true, properties from the Maven POM can be used as variables in the provisioning files.
     */
    @Parameter(defaultValue="false")
    protected boolean usePomVariables;
        
    /**
     * If set to true, the effective provisioning models with all variables replaced is attached instead of the raw model.
     */
    @Parameter(defaultValue="false")
    protected boolean attachEffectiveModel;
{code}

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