Doesn't it look like a kind of profile ? :)

Without joke, the fact to define a specific behavior for a given Karaf instance could be a profile.

I planned to add a section in the roadmap wiki page to distinguish:
- usage of features
- usage of kar
- the karaf profile background

Anyway Jamie, your proposal is interesting. Did you try to use the etc/custom.properties for that ? The custom.properties file has been introduced especially for custom configuration of a Karaf instance.

Regards
JB

On 02/16/2011 06:56 PM, jamie campbell wrote:
Hi,

I'm wondering if it's possible to have a compositional
etc/startup.properties in the same way one can have a compositional pom
(well, maybe pom is a bad comparison because I don't need repository
sync ability or any of the other fancy things a pom can do with regards
to composition). My use case is that I'd like to have a core set of
startup bits, and from that extensional startup bits that vary from one
scenario to another, so it would be sweet if I could do something like

------------
import base/base_startup.properties

org/specificUseCase/specificUseCase.jar=51
org/anothercase/another.jar=52
------------

-Jamie

Reply via email to