2014-09-22 17:13 GMT+02:00 Felix Meschberger <[email protected]>: > Hi > > Am 22.09.2014 um 17:09 schrieb Chetan Mehrotra <[email protected] > >: > > > On Mon, Sep 22, 2014 at 8:15 PM, Felix Meschberger <[email protected]> > wrote: > >> I think in this case we explicitly don’t want this: Also, this is not > the same as the case for 12factor configuration: This is basically just a > packing list to create a quick start. This is a build time task which > should result in a quick start which can be used over and over again. As > such, there is IMHO no need to depend on external variables. > > > > I thought the aim is to provide a single config file which captures > > all the required details and checked into source control. So > > deployment specific variables need to be factored out. For e.g. if the > > OSGi config mentioned in xml has entries for password/secret keys > > should they be made part of text or they are expected to be passed in > > via system props or env vars? > > Such things are not part of this configuration and the build at all. They > should always be „injected“ on deployment, I agree. > > Right, but there is nothing specific we have to do in the model about it. You need a way to inject this stuff on deployment, and this can be done with merging a deployment model into this model. And I guess there are other ways to do it.
Regards Carsten > Regards > Felix > > > > > Chetan Mehrotra > > -- Carsten Ziegeler Adobe Research Switzerland [email protected]
