[
https://issues.apache.org/jira/browse/SLING-4879?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14625848#comment-14625848
]
Stefan Seifert commented on SLING-4879:
---------------------------------------
the attachEffectiveModel has also a relevance fro SLING-4880, see description
there.
in both cases it would be possible to switch back to the raw model but replace
variables and dependencies from pom if "usePomVariables" or
"usePomDependencies" are switched to true. i initially re-used the "effecive
model" to do this replacements because i do not wanted to duplicate the logic
which duplicates a model and replaces some information in it. but this could be
separated and refacored of course.
do you think it is better to remove the "attachEffectiveModel" flag and
automatically update the variables block if "usePomVariables" is set to true?
> 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)