You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by Krzysztof Sobkowiak <kr...@gmail.com> on 2015/01/24 22:23:14 UTC
[DISCUSS] Command to populate full assembly (was: [DISCUSS] Which
assemblies to keep around?)
Hi
Almost one year ago we have decided to remove the full and minimal
distribution form ServiceMix 5. We have also decided to create a special
command (or extend the features command) to populate the system
repository with all bundles - it should be possible to use ServiceMix on
systems with no internet connections.
I think, we have we have done nothing in this theme. Please correct me
if there is already a solution in Karaf.
What do you propose? For me, the best solution would be a new command
(or new option in existing command) under the features commands.
We need at least a manual how to deal with this problem. I don't think
many people have problem with this, but we have at least one question:
http://stackoverflow.com/questions/28110588/apache-servicemix-5-1-4-full-version
Regards
Krzysztof
On 20.02.2014 12:09, Gert Vanthienen wrote:
> Hi Jean-Baptiste,
>
> Yeah, I think that extra flag on the feature:install command would be
> a nice extra. Sounds like there are already quite a few solutions
> available - perhaps we should create a page on the Karaf website to
> make people aware of the options for running a container without an
> internet connection? In my experience, this is not that uncommon a
> requirement.
>
> Regards
>
> Gert
>
> On Thu, Feb 20, 2014 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>> Hi Gert,
>>
>> On Karaf 3.x, kar:install populates the system repo.
>>
>> More over, some new goals on maven-karaf-plugin (like mvn karaf:deploy) will
>> populate the system repo (using scp).
>>
>> Another option is "bundle:install -p" (-p for persistent) which also
>> populate the system repo.
>>
>> Maybe we can add an option on the FeaturesService to also populate the
>> system repo (as bundle:install).
>>
>> Regards
>> JB
>>
>>
>> On 02/19/2014 08:23 PM, Gert Vanthienen wrote:
>>> L.S.,
>>>
>>>
>>> Looks like we have a consensus here - raised
>>> https://issues.apache.org/jira/browse/SM-2242 to keep track of this.
>>> For the command to populate the system directory for offline use,
>>> wouldn't it be better to add that to Karaf instead?
>>>
>>>
>>> Regards,
>>>
>>> Gert Vanthienen
>>>
>>>
>>> On Wed, Feb 19, 2014 at 8:03 PM, Cristiano Costantini
>>> <cr...@gmail.com> wrote:
>>>> +1 as Achim
>>>>
>>>>
>>>> 2014-02-19 19:57 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>>>>
>>>>> +1 for one distro and this special command to do fillup the system dir.
>>>>>
>>>>>
>>>>> 2014-02-19 19:29 GMT+01:00 Jon Anstey <ja...@gmail.com>:
>>>>>
>>>>>> +1
>>>>>>
>>>>>> Having one distro is going to make polishing/testing a lot easier too.
>>>>>> I
>>>>>> also like Raul's idea of having a command to fully populate the system
>>>>> dir
>>>>>> (or other dir) at a user's discretion.
>>>>>>
>>>>>>
>>>>>> On Wed, Feb 19, 2014 at 2:40 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>>>> wrote:
>>>>>>
>>>>>>> Hi guys,
>>>>>>>
>>>>>>> I don't see a lot of value to full assembly and minimal:
>>>>>>>
>>>>>>> - if an user wants minimal, just use Karaf ;)
>>>>>>> - if an user really want full, just install NMR/JBI, etc in your SMX.
>>>>>>>
>>>>>>> I would keep only default assembly which is ready to use and
>>>>> extensible.
>>>>>>>
>>>>>>> Regards
>>>>>>> JB
>>>>>>>
>>>>>>>
>>>>>>> On 02/19/2014 11:46 AM, Gert Vanthienen wrote:
>>>>>>>
>>>>>>>> L.S.,
>>>>>>>>
>>>>>>>>
>>>>>>>> Just noticed Krzysztof's comment about the how and why of the
>>>>>>>> apache-servicemix-full assembly in JIRA and think it's worth having a
>>>>>>>> quick discussion about which of these assemblies we want to keep
>>>>>>>> around going forward.
>>>>>>>>
>>>>>>>> Right now, we have 3 variations of our assembly in ServiceMix 5:
>>>>>>>> - The default assembly has a setup that includes the base CXF, Camel
>>>>>>>> and ActiveMQ bits and preinstalls those as boot features
>>>>>>>> - The minimal assembly actually has none of these things
>>>>>>>> preinstalled,
>>>>>>>> it's just a plain Karaf with the feature URLs (among a few other
>>>>>>>> things) preconfigured - not sure how much this one is used though
>>>>>>>> - The full assembly is identical to default assembly, but the /system
>>>>>>>> folder contains all bundles for all optional features. This makes it
>>>>>>>> easy for people to use ServiceMix on servers that have no direct
>>>>>>>> connection to the internet. This one is probably used a bit more (I
>>>>>>>> usually install this one myself), but we are struggling to keep it
>>>>>>>> below the maximum 350000000 bytes distribution size (which is already
>>>>>>>> an exception to the rule at the ASF) and as issue
>>>>>>>> https://issues.apache.org/jira/browse/SM-2241 is showing, it is prone
>>>>>>>> to be impacted by any kind of error in any of our dependencies'
>>>>>>>> features files.
>>>>>>>>
>>>>>>>> For ServiceMix 5 and other upcoming versions, which of these
>>>>>>>> assemblies do we want to keep around?
>>>>>>>>
>>>>>>>>
>>>>>>>> Regards,
>>>>>>>>
>>>>>>>> Gert Vanthienen
>>>>>>>>
>>>>>>>>
>>>>>>> --
>>>>>>> Jean-Baptiste Onofré
>>>>>>> jbonofre@apache.org
>>>>>>> http://blog.nanthrax.net
>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Cheers,
>>>>>> Jon
>>>>>> ---------------
>>>>>> Red Hat, Inc.
>>>>>> Email: janstey@redhat.com
>>>>>> Web: http://redhat.com
>>>>>> Twitter: jon_anstey
>>>>>> Blog: http://janstey.blogspot.com
>>>>>> Author of Camel in Action: http://manning.com/ibsen
>>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>>>> &
>>>>> Project Lead
>>>>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
>>>>> Commiter & Project Lead
>>>>> blog <http://notizblog.nierbeck.de/>
>>>>>
>> --
>> Jean-Baptiste Onofré
>> jbonofre@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
--
Krzysztof Sobkowiak
JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
@ ASF
Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
<http://www.pl.capgemini-sdm.com/> | Wroclaw
e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
Twitter: @KSobkowiak
Calendar: http://goo.gl/yvsebC
Re: [DISCUSS] Command to populate full assembly
Posted by Jean-Baptiste Onofré <jb...@nanthrax.net>.
As reminder, with Karaf 3.x, you have kar files, and the install-kar
goal of the karaf-maven-plugin.
Regards
JB
On 01/24/2015 11:15 PM, Gert Vanthienen wrote:
> L.S.,
>
>
> We do have this exact same problem with one of our customers. For
> them, we solved that problem by adding an assembly module to their
> project, that runs the add-features-to-repo goal and zips everything
> up. That way, we just deliver the ZIP file with all the bundles for
> all the features they need in there. Up to now, that solution has
> worked well and it gives them the ability to run offline without
> having to download bundles for all the features they don't need.
>
> Perhaps we should document this solution and/or add an archetype to
> make this easier (similar to the exisiting karaf-assembly-archetype,
> but without packaging up an entire container) for the Karaf 2.x based
> versions of ServiceMix? For ServiceMix 6, KARs should provide similar
> functionality out-of-the-box, so it might make more sense to document
> that instead?
>
>
> Regards,
>
> Gert Vanthienen
>
>
> On Sat, Jan 24, 2015 at 10:23 PM, Krzysztof Sobkowiak
> <kr...@gmail.com> wrote:
>> Hi
>>
>> Almost one year ago we have decided to remove the full and minimal
>> distribution form ServiceMix 5. We have also decided to create a special
>> command (or extend the features command) to populate the system
>> repository with all bundles - it should be possible to use ServiceMix on
>> systems with no internet connections.
>>
>> I think, we have we have done nothing in this theme. Please correct me
>> if there is already a solution in Karaf.
>>
>> What do you propose? For me, the best solution would be a new command
>> (or new option in existing command) under the features commands.
>>
>> We need at least a manual how to deal with this problem. I don't think
>> many people have problem with this, but we have at least one question:
>> http://stackoverflow.com/questions/28110588/apache-servicemix-5-1-4-full-version
>>
>> Regards
>> Krzysztof
>>
>>
>> On 20.02.2014 12:09, Gert Vanthienen wrote:
>>> Hi Jean-Baptiste,
>>>
>>> Yeah, I think that extra flag on the feature:install command would be
>>> a nice extra. Sounds like there are already quite a few solutions
>>> available - perhaps we should create a page on the Karaf website to
>>> make people aware of the options for running a container without an
>>> internet connection? In my experience, this is not that uncommon a
>>> requirement.
>>>
>>> Regards
>>>
>>> Gert
>>>
>>> On Thu, Feb 20, 2014 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>>> Hi Gert,
>>>>
>>>> On Karaf 3.x, kar:install populates the system repo.
>>>>
>>>> More over, some new goals on maven-karaf-plugin (like mvn karaf:deploy) will
>>>> populate the system repo (using scp).
>>>>
>>>> Another option is "bundle:install -p" (-p for persistent) which also
>>>> populate the system repo.
>>>>
>>>> Maybe we can add an option on the FeaturesService to also populate the
>>>> system repo (as bundle:install).
>>>>
>>>> Regards
>>>> JB
>>>>
>>>>
>>>> On 02/19/2014 08:23 PM, Gert Vanthienen wrote:
>>>>> L.S.,
>>>>>
>>>>>
>>>>> Looks like we have a consensus here - raised
>>>>> https://issues.apache.org/jira/browse/SM-2242 to keep track of this.
>>>>> For the command to populate the system directory for offline use,
>>>>> wouldn't it be better to add that to Karaf instead?
>>>>>
>>>>>
>>>>> Regards,
>>>>>
>>>>> Gert Vanthienen
>>>>>
>>>>>
>>>>> On Wed, Feb 19, 2014 at 8:03 PM, Cristiano Costantini
>>>>> <cr...@gmail.com> wrote:
>>>>>> +1 as Achim
>>>>>>
>>>>>>
>>>>>> 2014-02-19 19:57 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>>>>>>
>>>>>>> +1 for one distro and this special command to do fillup the system dir.
>>>>>>>
>>>>>>>
>>>>>>> 2014-02-19 19:29 GMT+01:00 Jon Anstey <ja...@gmail.com>:
>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Having one distro is going to make polishing/testing a lot easier too.
>>>>>>>> I
>>>>>>>> also like Raul's idea of having a command to fully populate the system
>>>>>>> dir
>>>>>>>> (or other dir) at a user's discretion.
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Feb 19, 2014 at 2:40 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi guys,
>>>>>>>>>
>>>>>>>>> I don't see a lot of value to full assembly and minimal:
>>>>>>>>>
>>>>>>>>> - if an user wants minimal, just use Karaf ;)
>>>>>>>>> - if an user really want full, just install NMR/JBI, etc in your SMX.
>>>>>>>>>
>>>>>>>>> I would keep only default assembly which is ready to use and
>>>>>>> extensible.
>>>>>>>>>
>>>>>>>>> Regards
>>>>>>>>> JB
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> On 02/19/2014 11:46 AM, Gert Vanthienen wrote:
>>>>>>>>>
>>>>>>>>>> L.S.,
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Just noticed Krzysztof's comment about the how and why of the
>>>>>>>>>> apache-servicemix-full assembly in JIRA and think it's worth having a
>>>>>>>>>> quick discussion about which of these assemblies we want to keep
>>>>>>>>>> around going forward.
>>>>>>>>>>
>>>>>>>>>> Right now, we have 3 variations of our assembly in ServiceMix 5:
>>>>>>>>>> - The default assembly has a setup that includes the base CXF, Camel
>>>>>>>>>> and ActiveMQ bits and preinstalls those as boot features
>>>>>>>>>> - The minimal assembly actually has none of these things
>>>>>>>>>> preinstalled,
>>>>>>>>>> it's just a plain Karaf with the feature URLs (among a few other
>>>>>>>>>> things) preconfigured - not sure how much this one is used though
>>>>>>>>>> - The full assembly is identical to default assembly, but the /system
>>>>>>>>>> folder contains all bundles for all optional features. This makes it
>>>>>>>>>> easy for people to use ServiceMix on servers that have no direct
>>>>>>>>>> connection to the internet. This one is probably used a bit more (I
>>>>>>>>>> usually install this one myself), but we are struggling to keep it
>>>>>>>>>> below the maximum 350000000 bytes distribution size (which is already
>>>>>>>>>> an exception to the rule at the ASF) and as issue
>>>>>>>>>> https://issues.apache.org/jira/browse/SM-2241 is showing, it is prone
>>>>>>>>>> to be impacted by any kind of error in any of our dependencies'
>>>>>>>>>> features files.
>>>>>>>>>>
>>>>>>>>>> For ServiceMix 5 and other upcoming versions, which of these
>>>>>>>>>> assemblies do we want to keep around?
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Regards,
>>>>>>>>>>
>>>>>>>>>> Gert Vanthienen
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>> jbonofre@apache.org
>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Cheers,
>>>>>>>> Jon
>>>>>>>> ---------------
>>>>>>>> Red Hat, Inc.
>>>>>>>> Email: janstey@redhat.com
>>>>>>>> Web: http://redhat.com
>>>>>>>> Twitter: jon_anstey
>>>>>>>> Blog: http://janstey.blogspot.com
>>>>>>>> Author of Camel in Action: http://manning.com/ibsen
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>>>>>> &
>>>>>>> Project Lead
>>>>>>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
>>>>>>> Commiter & Project Lead
>>>>>>> blog <http://notizblog.nierbeck.de/>
>>>>>>>
>>>> --
>>>> Jean-Baptiste Onofré
>>>> jbonofre@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>
>> --
>> Krzysztof Sobkowiak
>>
>> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
>> @ ASF
>> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
>> <http://www.pl.capgemini-sdm.com/> | Wroclaw
>> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
>> Twitter: @KSobkowiak
>> Calendar: http://goo.gl/yvsebC
--
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com
Re: [DISCUSS] Command to populate full assembly (was: [DISCUSS] Which
assemblies to keep around?)
Posted by Gert Vanthienen <ge...@gmail.com>.
L.S.,
We do have this exact same problem with one of our customers. For
them, we solved that problem by adding an assembly module to their
project, that runs the add-features-to-repo goal and zips everything
up. That way, we just deliver the ZIP file with all the bundles for
all the features they need in there. Up to now, that solution has
worked well and it gives them the ability to run offline without
having to download bundles for all the features they don't need.
Perhaps we should document this solution and/or add an archetype to
make this easier (similar to the exisiting karaf-assembly-archetype,
but without packaging up an entire container) for the Karaf 2.x based
versions of ServiceMix? For ServiceMix 6, KARs should provide similar
functionality out-of-the-box, so it might make more sense to document
that instead?
Regards,
Gert Vanthienen
On Sat, Jan 24, 2015 at 10:23 PM, Krzysztof Sobkowiak
<kr...@gmail.com> wrote:
> Hi
>
> Almost one year ago we have decided to remove the full and minimal
> distribution form ServiceMix 5. We have also decided to create a special
> command (or extend the features command) to populate the system
> repository with all bundles - it should be possible to use ServiceMix on
> systems with no internet connections.
>
> I think, we have we have done nothing in this theme. Please correct me
> if there is already a solution in Karaf.
>
> What do you propose? For me, the best solution would be a new command
> (or new option in existing command) under the features commands.
>
> We need at least a manual how to deal with this problem. I don't think
> many people have problem with this, but we have at least one question:
> http://stackoverflow.com/questions/28110588/apache-servicemix-5-1-4-full-version
>
> Regards
> Krzysztof
>
>
> On 20.02.2014 12:09, Gert Vanthienen wrote:
>> Hi Jean-Baptiste,
>>
>> Yeah, I think that extra flag on the feature:install command would be
>> a nice extra. Sounds like there are already quite a few solutions
>> available - perhaps we should create a page on the Karaf website to
>> make people aware of the options for running a container without an
>> internet connection? In my experience, this is not that uncommon a
>> requirement.
>>
>> Regards
>>
>> Gert
>>
>> On Thu, Feb 20, 2014 at 12:06 PM, Jean-Baptiste Onofré <jb...@nanthrax.net> wrote:
>>> Hi Gert,
>>>
>>> On Karaf 3.x, kar:install populates the system repo.
>>>
>>> More over, some new goals on maven-karaf-plugin (like mvn karaf:deploy) will
>>> populate the system repo (using scp).
>>>
>>> Another option is "bundle:install -p" (-p for persistent) which also
>>> populate the system repo.
>>>
>>> Maybe we can add an option on the FeaturesService to also populate the
>>> system repo (as bundle:install).
>>>
>>> Regards
>>> JB
>>>
>>>
>>> On 02/19/2014 08:23 PM, Gert Vanthienen wrote:
>>>> L.S.,
>>>>
>>>>
>>>> Looks like we have a consensus here - raised
>>>> https://issues.apache.org/jira/browse/SM-2242 to keep track of this.
>>>> For the command to populate the system directory for offline use,
>>>> wouldn't it be better to add that to Karaf instead?
>>>>
>>>>
>>>> Regards,
>>>>
>>>> Gert Vanthienen
>>>>
>>>>
>>>> On Wed, Feb 19, 2014 at 8:03 PM, Cristiano Costantini
>>>> <cr...@gmail.com> wrote:
>>>>> +1 as Achim
>>>>>
>>>>>
>>>>> 2014-02-19 19:57 GMT+01:00 Achim Nierbeck <bc...@googlemail.com>:
>>>>>
>>>>>> +1 for one distro and this special command to do fillup the system dir.
>>>>>>
>>>>>>
>>>>>> 2014-02-19 19:29 GMT+01:00 Jon Anstey <ja...@gmail.com>:
>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Having one distro is going to make polishing/testing a lot easier too.
>>>>>>> I
>>>>>>> also like Raul's idea of having a command to fully populate the system
>>>>>> dir
>>>>>>> (or other dir) at a user's discretion.
>>>>>>>
>>>>>>>
>>>>>>> On Wed, Feb 19, 2014 at 2:40 PM, Jean-Baptiste Onofré <jb@nanthrax.net
>>>>>>>> wrote:
>>>>>>>
>>>>>>>> Hi guys,
>>>>>>>>
>>>>>>>> I don't see a lot of value to full assembly and minimal:
>>>>>>>>
>>>>>>>> - if an user wants minimal, just use Karaf ;)
>>>>>>>> - if an user really want full, just install NMR/JBI, etc in your SMX.
>>>>>>>>
>>>>>>>> I would keep only default assembly which is ready to use and
>>>>>> extensible.
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>>
>>>>>>>> On 02/19/2014 11:46 AM, Gert Vanthienen wrote:
>>>>>>>>
>>>>>>>>> L.S.,
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Just noticed Krzysztof's comment about the how and why of the
>>>>>>>>> apache-servicemix-full assembly in JIRA and think it's worth having a
>>>>>>>>> quick discussion about which of these assemblies we want to keep
>>>>>>>>> around going forward.
>>>>>>>>>
>>>>>>>>> Right now, we have 3 variations of our assembly in ServiceMix 5:
>>>>>>>>> - The default assembly has a setup that includes the base CXF, Camel
>>>>>>>>> and ActiveMQ bits and preinstalls those as boot features
>>>>>>>>> - The minimal assembly actually has none of these things
>>>>>>>>> preinstalled,
>>>>>>>>> it's just a plain Karaf with the feature URLs (among a few other
>>>>>>>>> things) preconfigured - not sure how much this one is used though
>>>>>>>>> - The full assembly is identical to default assembly, but the /system
>>>>>>>>> folder contains all bundles for all optional features. This makes it
>>>>>>>>> easy for people to use ServiceMix on servers that have no direct
>>>>>>>>> connection to the internet. This one is probably used a bit more (I
>>>>>>>>> usually install this one myself), but we are struggling to keep it
>>>>>>>>> below the maximum 350000000 bytes distribution size (which is already
>>>>>>>>> an exception to the rule at the ASF) and as issue
>>>>>>>>> https://issues.apache.org/jira/browse/SM-2241 is showing, it is prone
>>>>>>>>> to be impacted by any kind of error in any of our dependencies'
>>>>>>>>> features files.
>>>>>>>>>
>>>>>>>>> For ServiceMix 5 and other upcoming versions, which of these
>>>>>>>>> assemblies do we want to keep around?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>>
>>>>>>>>> Gert Vanthienen
>>>>>>>>>
>>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Cheers,
>>>>>>> Jon
>>>>>>> ---------------
>>>>>>> Red Hat, Inc.
>>>>>>> Email: janstey@redhat.com
>>>>>>> Web: http://redhat.com
>>>>>>> Twitter: jon_anstey
>>>>>>> Blog: http://janstey.blogspot.com
>>>>>>> Author of Camel in Action: http://manning.com/ibsen
>>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Apache Karaf <http://karaf.apache.org/> Committer & PMC
>>>>>> OPS4J Pax Web <http://wiki.ops4j.org/display/paxweb/Pax+Web/> Committer
>>>>>> &
>>>>>> Project Lead
>>>>>> OPS4J Pax for Vaadin <http://team.ops4j.org/wiki/display/PAXVAADIN/Home>
>>>>>> Commiter & Project Lead
>>>>>> blog <http://notizblog.nierbeck.de/>
>>>>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>
> --
> Krzysztof Sobkowiak
>
> JEE & OSS Architect | Senior Solution Architect @ Capgemini | Committer
> @ ASF
> Capgemini <http://www.pl.capgemini.com/> | Software Solutions Center
> <http://www.pl.capgemini-sdm.com/> | Wroclaw
> e-mail: krzys.sobkowiak@gmail.com <ma...@gmail.com> |
> Twitter: @KSobkowiak
> Calendar: http://goo.gl/yvsebC