[jira] [Comment Edited] (SLING-8167) Using sling.home as a variable leads to runtime errors

["Karl Pauls (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/SLING-8167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16712838#comment-16712838 ] 

Karl Pauls edited comment on SLING-8167 at 12/7/18 1:14 PM:
------------------------------------------------------------

[~rombert], yes, that makes sense - it is not a workaround but works as designed as features have to "declare" all variables they need. However, I think we should improve the tooling to catch such situations and maybe WARN about them. Thanks for reporting!


was (Author: karlpauls):
[~rombert], yes, that makes sense - it is not a workaround but works as designed as features have to "declare" all variables they need. However, I think we should improve the tooling to at catch such situations and maybe WARN about them. Thanks for reporting!

> Using sling.home as a variable leads to runtime errors
> ------------------------------------------------------
>
>                 Key: SLING-8167
>                 URL: https://issues.apache.org/jira/browse/SLING-8167
>             Project: Sling
>          Issue Type: Bug
>          Components: Feature Model
>    Affects Versions: slingfeature-maven-plugin 0.8.0
>            Reporter: Robert Munteanu
>            Priority: Major
>             Fix For: slingfeature-maven-plugin 0.8.2
>
>
> I tried using ${sling.home} as a variable but replacement did not work and ended up failing at runtime when the property was used to try and create a directory, e.g. - failed creating directory "/${sling.home}/foo".
> I was able to work around by declaring a ${sling.home}: null variable but I wonder whether we can have better handling of such scenarios.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)