Mailing-List: contact dev-help@felix.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@felix.apache.org
Message-ID: <29411929.1191418013349.JavaMail.jira@brutus>
Date: Wed, 3 Oct 2007 06:26:53 -0700 (PDT)
From: "Richard S. Hall (JIRA)" <jira@apache.org>
To: dev@felix.apache.org
Subject: [jira] Commented: (FELIX-380) provide configuration.properties in
 the framework.jar by default
In-Reply-To: <24068826.1190819570600.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/FELIX-380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532099 ] 

Richard S. Hall commented on FELIX-380:
---------------------------------------

I had a, perhaps, simpler idea.

Couldn't we just define these properties in our parent POM (or some logical place) and simply have property substitution performed by Maven/bundleplugin?

> provide configuration.properties in the framework.jar by default
> ----------------------------------------------------------------
>
>                 Key: FELIX-380
>                 URL: https://issues.apache.org/jira/browse/FELIX-380
>             Project: Felix
>          Issue Type: Improvement
>          Components: Framework
>    Affects Versions: 1.0.0
>            Reporter: Costin Leau
>            Assignee: Richard S. Hall
>
> Even when using just the framework felix as an embedded library, it is helpful to have the default configuration.properties (which specifies the packages) loaded automatically and present in the jar.
> The configuration could be overwritten at startup so clients that want different packages can do that while clients that do not interact with this aspect can have a resonable default loaded for them (which is our case = Spring OSGi).
> Thanks.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.