Hello again;
just to give a background of my use case:
motivation:
* have a dynamic configuration-driven karaf instance
* which can self-update or re-configure itself on demand
solution
* periodic pull of configuration from configuration repository on github
* link karaf auto deploy folder to the remote configuration repository
* automatic deploy/un-deploy of features.xml and package.kar per
changes in the deploy folder
Thank you,
Andrei
-------- Original Message --------
Subject: Re: [PROPOSAL] Features autostart attribute
From: Andrei Pozolotin <[email protected]>
To: [email protected]
Date: Wed 15 Aug 2012 10:12:25 AM CDT
>
> Hello,
>
> per Achim suggestion, can I ask what is current status of this
>
> http://karaf.922171.n3.nabble.com/PROPOSAL-Features-autostart-attribute-td2992236.html
>
> Thank you,
>
> Andrei
>
> -------- Original Message --------
> Subject: Re: [PROPOSAL] Features autostart attribute
> From: Dan Tran <[email protected]>
> To: [email protected]
> Date: Fri 06 Jan 2012 08:16:31 PM CST
>> Hi
>>
>> where are we with auto deploy/install/start discussion?
>>
>> -D
>>
>>
>>
>> On Wed, Oct 12, 2011 at 8:03 AM, Ioannis Canellos <[email protected]> wrote:
>>> I like the idea of profiles and I can see a lot of use case for profiles. If
>>> we use them exactly as maven does they will be also easier to understand.
>>> However, I think that the profiles concept is a totally different story. The
>>> use case here is quite simple and an approach like install="manual" would
>>> fit more.
>>>
>>> --
>>> *Ioannis Canellos*
>>> *
>>> FuseSource <http://fusesource.com>
>>>
>>> **
>>> Blog: http://iocanel.blogspot.com
>>> **
>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>> Apache ServiceMix <http://servicemix.apache.org/> Committer
>>> Apache Gora <http://incubator.apache.org/gora/> Committer
>>> *
>