You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Carsten Ziegeler (JIRA)" <ji...@apache.org> on 2008/12/22 08:54:44 UTC
[jira] Created: (SLING-793) Improve property file includes
Improve property file includes
------------------------------
Key: SLING-793
URL: https://issues.apache.org/jira/browse/SLING-793
Project: Sling
Issue Type: Improvement
Affects Versions: Launchpad Base 2.0.2
Reporter: Carsten Ziegeler
Fix For: Launchpad Base 2.0.4
To include own property files with startup information, an include statement needs to be added to the sling.properties file.
An exception is the "jcr-client.properties" file which is a hard-coded include in launchpad.
It would be nice to be able to add own property files by convention instead of configuration. This would allow to use the sling.properties from launchpad base untouched by just adding additional files.
I think the convention could use some filename conventions, so all files names "*-sling.properties" are included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (SLING-793) Improve property file includes
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler closed SLING-793.
----------------------------------
Resolution: Won't Fix
I think that fragment bundles are the better option; therefore closing this bug.
> Improve property file includes
> ------------------------------
>
> Key: SLING-793
> URL: https://issues.apache.org/jira/browse/SLING-793
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.0.2
> Reporter: Carsten Ziegeler
> Fix For: Launchpad Base 2.0.4
>
>
> To include own property files with startup information, an include statement needs to be added to the sling.properties file.
> An exception is the "jcr-client.properties" file which is a hard-coded include in launchpad.
> It would be nice to be able to add own property files by convention instead of configuration. This would allow to use the sling.properties from launchpad base untouched by just adding additional files.
> I think the convention could use some filename conventions, so all files names "*-sling.properties" are included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SLING-793) Improve property file includes
Posted by "Carsten Ziegeler (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carsten Ziegeler updated SLING-793:
-----------------------------------
Component/s: Launchpad
> Improve property file includes
> ------------------------------
>
> Key: SLING-793
> URL: https://issues.apache.org/jira/browse/SLING-793
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.0.2
> Reporter: Carsten Ziegeler
> Fix For: Launchpad Base 2.0.4
>
>
> To include own property files with startup information, an include statement needs to be added to the sling.properties file.
> An exception is the "jcr-client.properties" file which is a hard-coded include in launchpad.
> It would be nice to be able to add own property files by convention instead of configuration. This would allow to use the sling.properties from launchpad base untouched by just adding additional files.
> I think the convention could use some filename conventions, so all files names "*-sling.properties" are included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (SLING-793) Improve property file includes
Posted by "Felix Meschberger (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SLING-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12704257#action_12704257 ]
Felix Meschberger commented on SLING-793:
-----------------------------------------
I am not sure about this jcr-client.properties file ... I could not find any reference.
But actually, the sling.properties file contains an entry:
#
# Include properties to install additional assemblies such as JCR support
# Core Sling etc.
sling.include.install = sling_install.properties
So, by default a sling_install.properties file may be included.
Yet, I am not sure, whether we really need such a functionality...
> Improve property file includes
> ------------------------------
>
> Key: SLING-793
> URL: https://issues.apache.org/jira/browse/SLING-793
> Project: Sling
> Issue Type: Improvement
> Components: Launchpad
> Affects Versions: Launchpad Base 2.0.2
> Reporter: Carsten Ziegeler
> Fix For: Launchpad Base 2.0.4
>
>
> To include own property files with startup information, an include statement needs to be added to the sling.properties file.
> An exception is the "jcr-client.properties" file which is a hard-coded include in launchpad.
> It would be nice to be able to add own property files by convention instead of configuration. This would allow to use the sling.properties from launchpad base untouched by just adding additional files.
> I think the convention could use some filename conventions, so all files names "*-sling.properties" are included.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.