I think the correct public url is https://github.com/djencks/karaf/tree/feature

Anyone can check it out using the following commands in an empty directory:
   git clone https://github.com/djencks/karaf.git
   cd karaf
   git checkout feature

On Mon, Jan 24, 2011 at 22:07, David Jencks <[email protected]> wrote:
>
> On Jan 24, 2011, at 12:52 PM, Chris Custine wrote:
>
>> I like all of these ideas, each for different use cases.  I do like
>> what David is suggesting as it would make a lot of sense for packaging
>> applications based on Karaf, which seems to be a common use case right
>> now.  This is fairly close to what Gert and I have discussed on
>> several occasions, but nobody has had time to pursue it.
>
> I'd certainly like to know how what you have in mind relates to what I've 
> been implementing.
>
>>
>> David, I might have missed the links in other emails, is your work on
>> Github in a public repo?
>
> See the "Possible feature features" thread. As mentioned there the code needs 
> some cleanup.  I'm just learning about git and github so I'm not sure how 
> public this is -- if there's anything I can do to make it more public or add 
> people as collaborators let me know.
>
> Github shows a http url of https://[email protected]/djencks/karaf.git
> I'd guess you'd leave out the djencks@ part???
>
> It's in the "feature" branch.
>
> thanks
> david jencks
>>
>> Chris
>> --
>> Chris Custine
>> FuseSource - Open Source Integration:: http://fusesource.com
>> My Blog :: http://blog.organicelement.com
>>
>>
>>
>>
>>
>> On Mon, Jan 24, 2011 at 12:49, David Jencks <[email protected]> wrote:
>>> Hi,
>>>
>>> My idea is actually that what we expect users to do is create their own 
>>> profile adapted to their particular apps, rather than relying on the 
>>> particular selection of subsystems or components we think might be useful.  
>>> While the mojos I've been working on at github let you assemble most of the 
>>> profiles you mention easily, my ultimate goal is to make it easier to 
>>> assemble a custom server than deploy stuff into an existing profile server.
>>>
>>> thanks
>>> david jencks
>>>
>>>
>>> On Jan 24, 2011, at 10:13 AM, Jean-Baptiste Onofré wrote:
>>>
>>>> Hi Charles,
>>>>
>>>> Agree for that.
>>>> However I think in a short term enhancement. I think that we need to 
>>>> design something more generic and flexible.
>>>> I already quickly discussed of that with Guillaume.
>>>>
>>>> I propose to think about Karaf profiles. A profile is based on instance 
>>>> but enhanced and improved.
>>>>
>>>> For instance, we can see the following profiles:
>>>> 1/ micro kernel: corresponding to the minimal dist
>>>> 2/ default: corresponding to the "normal" current dist
>>>> 3/ mobile: for android
>>>> 4/ enterprise: providing enterprise application server based on enterprise 
>>>> features/arirs
>>>> 5/ esb: corresponding to ServiceMix/swordfish
>>>>
>>>> I have to think deeper around to design it. Maybe we can start a wiki page 
>>>> to brainstorm about it.
>>>>
>>>> Regards
>>>> JB
>>>>
>>>> On 01/24/2011 05:27 PM, Charles Moulliard wrote:
>>>>> Hi,
>>>>>
>>>>> I would like to start a discussion concerning the idea to generate
>>>>> during assembly of Apache Karaf a version who can be run on Google
>>>>> Android platform (Mobile Device).
>>>>>
>>>>> The existing process is quite tedious and could be simplified
>>>>>
>>>>> export PATH=<path-to-android>/tools:$PATH
>>>>> cd bin
>>>>> dx --dex --output=classes.dex felix.jar
>>>>> aapt add felix.jar classes.dex
>>>>> Prepare the bundle JARS:
>>>>>
>>>>> cd bundle
>>>>> dx --dex --output=classes.dex org.apache.felix.shell-1.0.0.jar
>>>>> aapt add org.apache.felix.shell-1.0.0.jar classes.dex
>>>>> dx --dex --output=classes.dex org.apache.felix.shell.tui-1.0.0.jar
>>>>> aapt add org.apache.felix.shell.tui-1.0.0.jar classes.dex
>>>>> dx --dex --output=classes.dex EnglishDictionary.jar
>>>>> aapt add EnglishDictionary.jar classes.dex
>>>>> dx --dex --output=classes.dex FrenchDictionary.jar
>>>>> aapt add FrenchDictionary.jar classes.dex
>>>>> dx --dex --output=classes.dex SpellChecker.jar
>>>>> aapt add SpellChecker.jar classes.dex
>>>>> Transfer all of them to the emulator (note that you need some kind of
>>>>> unix-like shell, such as the Mac OS X terminal or Linux):
>>>>>
>>>>> cd osgi-android
>>>>> emulator&
>>>>> find * -type f -exec adb push {} /data/felix/{} \;
>>>>>
>>>>> Some maven plugins exist and could be used to generate DEX files
>>>>> required by Davik Virtual Machine -->
>>>>>
>>>>> http://maven-android-plugin-m2site.googlecode.com/svn/dex-mojo.html
>>>>> http://www.sonatype.com/books/mvnref-book/reference/android-dev-sect-custom-details.html
>>>>>
>>>>> Running Apache Karaf on Android platform could be of great interest as
>>>>> it could allow the deployment of ActiveMQ and usage in offline mode on
>>>>> Mobile.
>>>>>
>>>>> What do you think about that ?
>>>>>
>>>>> Regards,
>>>>>
>>>>> Charles Moulliard
>>>>>
>>>>> Sr. Principal Solution Architect - FuseSource
>>>>> Apache Committer
>>>>>
>>>>> Blog : http://cmoulliard.blogspot.com
>>>>> Twitter : http://twitter.com/cmoulliard
>>>>> Linkedin : http://www.linkedin.com/in/charlesmoulliard
>>>>> Skype: cmoulliard
>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> ---------------------------------
>>>> HomePage
>>>> http://www.nanthrax.net
>>>> ---------------------------------
>>>> Contacts
>>>> [email protected]
>>>> [email protected]
>>>> ---------------------------------
>>>> OpenSource
>>>> BuildProcess/AutoDeploy
>>>> http://buildprocess.sourceforge.net
>>>> Apache ServiceMix
>>>> http://servicemix.apache.org
>>>> -----------------------------------
>>>> PGP : 17D4F086
>>>
>>>
>
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Reply via email to