karaf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jean-Baptiste Onofré ...@nanthrax.net>
Subject Re: Karaf 2.2.3 and Camel 2.8.0
Date Mon, 05 Sep 2011 09:17:44 GMT
Unfortunately, for now, I don't see other way to "inform" the users.

We have a new feature in the TODO list to handle this kind of situation: 
the feature trigger. The feature trigger allows us to call commands. In 
this case, you would call:

echo "Be sure to install the ORM implementation before the spring-orm 
feature"

But it's not yet available.

Regards
JB

On 09/05/2011 11:13 AM, Andreas Pieber wrote:
> I'm not convinced that ppl read faq sections, but this would be a good
> location otherwise
>
> Kind regards Andreas
> On Sep 5, 2011 11:09 AM, "Achim Nierbeck"<bcanhome@googlemail.com>  wrote:
>> Hi JB,
>>
>> I'm not sure that just setting a "note" is sufficient, we should more
>> "warn" about it, cause this will definitely
>> pop up as "bug". So maybe it could be placed somewhere "prominent" :)
>>
>> regards, Achim
>>
>> 2011/9/5 Jean-Baptiste Onofré<jb@nanthrax.net>:
>>> Hi Achim,
>>>
>>> I added the spring-orm feature. We have to document that the users have
> to
>>> install the ORM implementation before the spring-orm feature.
>>> In the same area, I also added a spring-struts feature. To avoid to
> "force"
>>> the Struts version, the users have to choose and install the Struts
> bundle
>>> before installing the spring-struts feature.
>>>
>>> I think that just a note in the Karaf user guide is enough.
>>>
>>> Regards
>>> JB
>>>
>>> On 09/05/2011 10:58 AM, Achim Nierbeck wrote:
>>>>
>>>> Hi JB,
>>>>
>>>> I'm +1 for all of these,
>>>>
>>>> just a little reminder that we need to think about how to handle the
>>>> Spring-ORM Bundle correctly.
>>>> The issue with the spring-orm bundle is that it imports all kind of
>>>> orm implementations like Hibernate, if those optional dependencies are
>>>> installed after the ORM bundle those Packages can not be seen.
>>>>
>>>> regards, Achim
>>>>
>>>> 2011/9/5 Freeman Fang<freeman.fang@gmail.com>:
>>>>>
>>>>> Sounds good to me.
>>>>>
>>>>> Regards
>>>>> Freeman
>>>>> On 2011-9-5, at 上午1:03, Jean-Baptiste Onofré wrote:
>>>>>
>>>>>> I got your point but:
>>>>>>
>>>>>> - for a general point of view, I still think that Karaf should provide
>>>>>> all
>>>>>> features for all Spring version, else, it means that we can't Sound
> the
>>>>>> spring version used by the others applications like Camel or CXF
>>>>>> - we should have named Karaf 2.3.0 in place of 2.2.3 to address this
>>>>>> kind
>>>>>> of major update. As reminder, we update to Spring 3.0.6 and add the
>>>>>> spring-jms feature to be able to install/support CXF 2.5.0.
>>>>>>
>>>>>> What we can do:
>>>>>> - in Karaf 2.2.4, rollback to Spring 3.0.5 and so be sure that Camel
>>>>>> 2.8.x
>>>>>> and CXF 2.4.x are supported.
>>>>>> - create a Karaf 2.3.x branch (waiting for the 3.0.0), which is
> exactly
>>>>>> like 2.2.x but including Spring 3.0.6.RELEASE (I have to talk with
the
>>>>>> Karaf
>>>>>> team about that, and I put it in copy)
>>>>>>
>>>>>> WDYT ?
>>>>>>
>>>>>> Regards
>>>>>> JB
>>>>>>
>>>>>> On 09/04/2011 01:52 PM, Freeman Fang wrote:
>>>>>>>
>>>>>>> Hi JB,
>>>>>>>
>>>>>>> To be honest I'm a lit bit concern about this solution.
>>>>>>> If Karaf 2.2.4 ship spring 3.0.6 anyway, even it cover all spring
>>>>>>> related bundles, and camel can refer those spring features using
>>>>>>> version
>>>>>>> range(it might be ok during resolve, but don't forget cxf 2.4.2
>>>>>>> features.xml still have srping-jms(3.0.5) feature directly and
it's
> not
>>>>>>> from karaf, :-)), however it still means the OSGi container provided
>>>>>>> spring version is 3.0.6, but the cxf(2.4.2) and camel(2.8.1)
which
> will
>>>>>>> be running in this container are still with spring 3.0.5, it
MIGHT be
>>>>>>> ok
>>>>>>> with spring 3.0.6 but we can't be that sure(as spring is a kind
of
>>>>>>> fundamental libs for lots of other projects), right?
>>>>>>>
>>>>>>> So I suggest either karaf 2.2.4 revert to spring 3.0.5(lit bit
weird
> to
>>>>>>> me) or camel 2.8.1 should stay with karaf 2.2.2.
>>>>>>>
>>>>>>> Regards
>>>>>>> Freeman
>>>>>>> On 2011-9-4, at 下午3:30, Jean-Baptiste Onofré wrote:
>>>>>>>
>>>>>>>> Hi Claus,
>>>>>>>>
>>>>>>>> I'm going to work on Karaf Spring features today and tomorrow
and
> test
>>>>>>>> it with Camel, CXF and ActiveMQ.
>>>>>>>> The 2.2.4 could contain only this and one other issue (about
JMX).
> So
>>>>>>>> it could be ready by tomorrow evening, and we can cut off
the
> release
>>>>>>>> on Tuesday.
>>>>>>>>
>>>>>>>> So I think that we could be inline for Camel 2.8.1.
>>>>>>>>
>>>>>>>> Is it OK for you ?
>>>>>>>>
>>>>>>>> Regards
>>>>>>>> JB
>>>>>>>>
>>>>>>>> On 09/04/2011 09:24 AM, Claus Ibsen wrote:
>>>>>>>>>
>>>>>>>>> On Sun, Sep 4, 2011 at 8:29 AM, Jean-Baptiste Onofré<
> jb@nanthrax.net>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> Hi Achim and all,
>>>>>>>>>>
>>>>>>>>>> I propose:
>>>>>>>>>> 1. to cover all Spring bundles in different Karaf
spring features
>>>>>>>>>> including
>>>>>>>>>> spring-tx
>>>>>>>>>> 2. release Karaf 2.2.4 soon with this change
>>>>>>>>>> 3. update Camel features descriptor to use the Karaf
spring-tx
>>>>>>>>>> features (and
>>>>>>>>>> eventually others, I have to check)
>>>>>>>>>> 4. release Camel 2.8.1
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> How soon can Karaf 2.2.4 be released?
>>>>>>>>>
>>>>>>>>> Would it speed up if the release was based on the 2.2.3
tags, and
>>>>>>>>> either did
>>>>>>>>> - a) revert back to Spring 3.0.5
>>>>>>>>> - b) bullet #1 above from Jean
>>>>>>>>>
>>>>>>>>> eg so there are no other changes and thus a confort in
the
> community
>>>>>>>>> that Karaf 2.2.4 is a patch release with this single
fix to ensure
>>>>>>>>> using Karaf + Camel runs smoothly. As its to be used
for the next
> SMX
>>>>>>>>> release as well.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> WDYT ?
>>>>>>>>>>
>>>>>>>>>> Regards
>>>>>>>>>> JB
>>>>>>>>>>
>>>>>>>>>> On 09/03/2011 09:38 PM, Achim Nierbeck wrote:
>>>>>>>>>>>
>>>>>>>>>>> Hi JB,
>>>>>>>>>>>
>>>>>>>>>>> I'm +1 on that one, often I was missing the spring-tx
feature in
>>>>>>>>>>> the
>>>>>>>>>>> first place :)
>>>>>>>>>>>
>>>>>>>>>>> regards, Achim
>>>>>>>>>>>
>>>>>>>>>>> Am 03.09.2011 18:54, schrieb Jean-Baptiste Onofré:
>>>>>>>>>>>>
>>>>>>>>>>>> Hi,
>>>>>>>>>>>>
>>>>>>>>>>>> I checked the issue and the problem is about
the spring-tx
> bundle.
>>>>>>>>>>>>
>>>>>>>>>>>> spring-tx bundle is not installed by a Karaf
features, the first
>>>>>>>>>>>> feature which install it is camel-jms (part
of the
> camel-spring).
>>>>>>>>>>>>
>>>>>>>>>>>> That's why we have a bundle version mismatch
between the spring
>>>>>>>>>>>> bundles provides by Karaf spring* features,
and the one provided
>>>>>>>>>>>> by
>>>>>>>>>>>> Camel features.
>>>>>>>>>>>>
>>>>>>>>>>>> I think that it makes sense that Karaf provides
all Spring*
>>>>>>>>>>>> features,
>>>>>>>>>>>> convering all spring bundle, and Camel just
"uses" it.
>>>>>>>>>>>>
>>>>>>>>>>>> I'm going to discuss with the team to see
how we move.
>>>>>>>>>>>>
>>>>>>>>>>>> Regards
>>>>>>>>>>>> JB
>>>>>>>>>>>>
>>>>>>>>>>>> On 09/02/2011 10:50 PM, mgardiner wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>> I have recently tried using Karaf 2.2.3
which has just updated
> to
>>>>>>>>>>>>> use
>>>>>>>>>>>>> Spring
>>>>>>>>>>>>> 3.0.6.RELEASE and we are now getting
conflicts in camel-jms
> 2.8.0
>>>>>>>>>>>>> because
>>>>>>>>>>>>> two versions of spring are available.
With a new camel release
>>>>>>>>>>>>> underway are
>>>>>>>>>>>>> you considering upgrading camel to spring
3.0.6.RELEASE?
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Here's the output
>>>>>>>>>>>>>
>>>>>>>>>>>>> Error executing command: Could not start
bundle
>>>>>>>>>>>>> mvn:org.apache.camel/camel-jms/2.8.0
in feature(s)
>>>>>>>>>>>>> camel-jms-2.8.0:
>>>>>>>>>>>>> Unable
>>>>>>>>>>>>> to resolve module org.apache.camel.camel-jms
[88.0] because it
> is
>>>>>>>>>>>>> exposed to
>>>>>>>>>>>>> package 'org.springframework.util' from
> org.springframework.core
>>>>>>>>>>>>> [82.0] and
>>>>>>>>>>>>> org.springframework.core [43.0] via two
dependency chains.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Chain 1:
>>>>>>>>>>>>> org.apache.camel.camel-jms [88.0]
>>>>>>>>>>>>> import:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> (&(package=org.springframework.util)(version>=3.0.0)(!(version>=4.0.0)))
>>>>>>>>>>>>>
>>>>>>>>>>>>> |
>>>>>>>>>>>>> export: package=org.springframework.util
>>>>>>>>>>>>> org.springframework.core [82.0]
>>>>>>>>>>>>>
>>>>>>>>>>>>> Chain 2:
>>>>>>>>>>>>> org.apache.camel.camel-jms [88.0]
>>>>>>>>>>>>> import:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> (&(package=org.apache.camel.impl)(version>=2.8.0)(!(version>=2.9.0)))
>>>>>>>>>>>>>
>>>>>>>>>>>>> |
>>>>>>>>>>>>> export: package=org.apache.camel.impl;
>>>>>>>>>>>>> uses:=org.springframework.jmx.export.annotation
>>>>>>>>>>>>> org.apache.camel.camel-core [80.0]
>>>>>>>>>>>>> import:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> (&(package=org.springframework.jmx.export.annotation)(version>=3.0.0)(!(version>=4.0.0)))
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> |
>>>>>>>>>>>>> export: package=org.springframework.jmx.export.annotation;
>>>>>>>>>>>>> uses:=org.springframework.aop.target
>>>>>>>>>>>>> org.springframework.context [48.0]
>>>>>>>>>>>>> import:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> (&(package=org.springframework.aop.target)(version>=3.0.6)(!(version>=3.0.7)))
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> |
>>>>>>>>>>>>> export: package=org.springframework.aop.target;
>>>>>>>>>>>>> uses:=org.springframework.core
>>>>>>>>>>>>> org.springframework.aop [47.0]
>>>>>>>>>>>>> import:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> (&(package=org.springframework.core)(version>=3.0.6)(!(version>=3.0.7)))
>>>>>>>>>>>>>
>>>>>>>>>>>>> |
>>>>>>>>>>>>> export: package=org.springframework.core;
>>>>>>>>>>>>> uses:=org.springframework.util
>>>>>>>>>>>>> export: package=org.springframework.util
>>>>>>>>>>>>> org.springframework.core [43.0]
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> --
>>>>>>>>>>>>> View this message in context:
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>
> http://camel.465427.n5.nabble.com/Karaf-2-2-3-and-Camel-2-8-0-tp4763828p4763828.html
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>> Sent from the Camel - Users mailing list
archive at Nabble.com.
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Jean-Baptiste Onofré
>>>>>>>>>> jbonofre@apache.org
>>>>>>>>>> http://blog.nanthrax.net
>>>>>>>>>> Talend - http://www.talend.com
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> jbonofre@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>
>>>>>>> ---------------------------------------------
>>>>>>> Freeman Fang
>>>>>>>
>>>>>>> FuseSource
>>>>>>> Email:ffang@fusesource.com
>>>>>>> Web: fusesource.com
>>>>>>> Twitter: freemanfang
>>>>>>> Blog: http://freemanfang.blogspot.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Jean-Baptiste Onofré
>>>>>> jbonofre@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>
>>>>> ---------------------------------------------
>>>>> Freeman Fang
>>>>>
>>>>> FuseSource
>>>>> Email:ffang@fusesource.com
>>>>> Web: fusesource.com
>>>>> Twitter: freemanfang
>>>>> Blog: http://freemanfang.blogspot.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> Jean-Baptiste Onofré
>>> jbonofre@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>
>>
>>
>> --
>> --
>> *Achim Nierbeck*
>>
>>
>> Apache Karaf<http://karaf.apache.org/>  Committer&  PMC
>> OPS4J Pax Web<http://wiki.ops4j.org/display/paxweb/Pax+Web/>
>> Committer&  Project Lead
>> blog<http://notizblog.nierbeck.de/>
>

-- 
Jean-Baptiste Onofré
jbonofre@apache.org
http://blog.nanthrax.net
Talend - http://www.talend.com

Mime
View raw message