Hello,
bumping up this thread. If there is no objection to the proposal, I'll
merge the PR and we can however have further discussion in the future. I'm
not planning to work on it in the very short term, but it would be good to
have a signoff so, we'll have a clear scope when we start that work.
C
Hi Cameleers,
in the past we had discussed the MDC and the opportunity to eventually
deprecate it. I understand that the feature, although old fashioned, still
has some good use case scenarios. However, the way it's actually
implemented in Camel is making its management and evolution a bit
difficul
camel-aws component were dropped from 3.9.0
>> because they are deprecated but I can't see the new camel-aws2 features.
>>
>> Is there a reason to not create the new features based on camel-aws2
>> components?
>>
>> May be I missed something.
>>
>> regards,
>>
>> --
>> François
>> fpa...@apache.org
>>
>>
amel 3. You're welcome to help.
>
> Il lun 5 lug 2021, 11:52 ha scritto:
>
>> Hi,
>>
>> I can see that all the camel-aws component were dropped from 3.9.0
>> because they are deprecated but I can't see the new camel-aws2 features.
>>
>> Is ther
deprecated but I can't see the new camel-aws2 features.
>
> Is there a reason to not create the new features based on camel-aws2
> components?
>
> May be I missed something.
>
> regards,
>
> --
> François
> fpa...@apache.org
>
>
Hi,
I can see that all the camel-aws component were dropped from 3.9.0
because they are deprecated but I can't see the new camel-aws2 features.
Is there a reason to not create the new features based on camel-aws2
components?
May be I missed something.
regards,
--
François
fpa...@apache.org
Github user onderson closed the pull request at:
https://github.com/apache/camel/pull/2458
---
GitHub user onderson opened a pull request:
https://github.com/apache/camel/pull/2458
CAMEL-12549 - fix karaf features except upgrading camel-script karaf
and the component
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Github user oscerd closed the pull request at:
https://github.com/apache/camel/pull/2197
---
GitHub user alb-i986 opened a pull request:
https://github.com/apache/camel/pull/2197
BOM: add cxf-rt-features-logging
CXF logging interceptors are now in a separate module.
See also http://cxf.apache.org/docs/message-logging.html
You can merge this pull request into a Git
sage in context:
http://camel.465427.n5.nabble.com/camel-spring-dm-feature-incompatible-to-most-other-features-of-camel-2-18-3-tp5796032p5797523.html
Sent from the Camel Development mailing list archive at Nabble.com.
ne, should work ok. I'll test that.
--
View this message in context:
http://camel.465427.n5.nabble.com/camel-spring-dm-feature-incompatible-to-most-other-features-of-camel-2-18-3-tp5796032p5797513.html
Sent from the Camel Development mailing list archive at Nabble.com.
Hi
Just in case we going to disable it so its not in the features file.
But the JAR is still build and released
Then it can be dropped/removed totally in 2.20 or 3.0 at the latest.
On Tue, Apr 11, 2017 at 3:41 PM, Claus Ibsen wrote:
> Hi
>
> Just a heads up that as spring-dm
Thu, Mar 23, 2017 at 6:01 PM, Christian Schneider
> wrote:
>> I also think removing spring dm for camel 2.19 is a good idea.
>> Currently people just mix camel-spring-dm with any other camel features and
>> expect it to work. So they can only be disappointed.
>>
>>
Logged a ticket
https://issues.apache.org/jira/browse/CAMEL-11059
On Thu, Mar 23, 2017 at 6:01 PM, Christian Schneider
wrote:
> I also think removing spring dm for camel 2.19 is a good idea.
> Currently people just mix camel-spring-dm with any other camel features and
> expect it to
I also think removing spring dm for camel 2.19 is a good idea.
Currently people just mix camel-spring-dm with any other camel features
and expect it to work. So they can only be disappointed.
Christian
On 23.03.2017 17:50, Claus Ibsen wrote:
I think you can run camel-spring-dm and maybe not
I think you can run camel-spring-dm and maybe not install components
that require Spring 4.x etc and then do some limited Camel application
on the legacy Spring DM. Or in theory have spring 3.x and 4.x run side
by side (osgi versioning) and have it somehow work. But hey f...
spring-dm is not good i
Camel 2.18.3 seems to have upgraded most camel modules to spring 4.
The only exemption is the camel-spring-dm feature which depends on
spring < 4.
As far as I know this causes camel 2.18.3 to not work on karaf when
using camel-spring-dm with any of the other camel modules that require
spring
On 12/07/2016 04:20 PM, Matt Pavlovich wrote:
Kicking off a discussion on what folks would like to see in 2.0.0
release for Artemis. My thought is that we should target ActiveMQ 5.x
feature parity in an effort to solidify Artemis in the product sense.
I will detail out specifics from my previou
Yep.. email client auto-address nuked me. Please disregard.
On 12/7/16 4:27 PM, Andrea Cosentino wrote:
I guess this is the wrong mailing lista..
Il mer, 7 dic, 2016 alle 22:20, Matt Pavlovich ha scritto: Kicking off a discussion on what folks would like to see in 2.0.0
release for Art
I guess this is the wrong mailing lista..
Il mer, 7 dic, 2016 alle 22:20, Matt Pavlovich ha
scritto: Kicking off a discussion on what folks would like to see in 2.0.0
release for Artemis. My thought is that we should target ActiveMQ 5.x
feature parity in an effort to solidify Artemis in t
Kicking off a discussion on what folks would like to see in 2.0.0
release for Artemis. My thought is that we should target ActiveMQ 5.x
feature parity in an effort to solidify Artemis in the product sense. I
will detail out specifics from my previous note on 5.x-Artemis feature gaps.
Thoughts?
PMC Member | Apache Camel committer
Apache Incubator PMC Member
https://www.linkedin.com/pub/christian-mueller/11/551/642
On Thu, Aug 20, 2015 at 9:30 AM, Bilgin Ibryam wrote:
> Validating features on trunk has been failing for a long time for me. Has
> anyone else faced it, do I need to do some
Validating features on trunk has been failing for a long time for me. Has
anyone else faced it, do I need to do some configurations?
The error I get is related to spring feature:
Unable to find definition for feature spring (version [3.2,4))
--
Bilgin Ibryam
Red Hat, Inc.
Apache Camel
Github user kcbabo closed the pull request at:
https://github.com/apache/camel/pull/415
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
GitHub user kcbabo opened a pull request:
https://github.com/apache/camel/pull/415
CAMEL-8332: Additional features for camel-dozer component
This commit includes the following changes:
* Added a new converter which allows the user to evaluate an expression
using Camel language
running.
Thanks.
[INFO]
[ERROR] Failed to execute goal
org.apache.karaf.tooling:features-maven-plugin:2.4.1:validate (validate) on
project apache-camel: Unable to validate F:
\Projects\Java\camel\platforms\karaf\features\target
with a BUNCH of restrictions)
> to use Spring 4 in OSGi, just not with spring-dm. Thus, allowing the
> import is important.
>
> However, for the karaf features.xml file, I restricted it to 3.x since the
> features file also installs spring-dm. Thus, when using Karaf, you will
> get
, for the karaf features.xml file, I restricted it to 3.x since the
features file also installs spring-dm. Thus, when using Karaf, you will get
spring3.2.x and spring-dm. The tests thus pass (other than a couple tests
that are failing for me, but they are failing without this change as well
a:304)
at java.lang.Thread.run(Thread.java:744)
I am reverting the import range to limit spring as 3.x
On Thu, Oct 30, 2014 at 7:35 PM, wrote:
> Repository: camel
> Updated Branches:
> refs/heads/master 3e77f050d -> f1b2010b1
>
>
> CAMEL-7887: Executing of 'mvn c
: willemjiang
Weibo: 姜宁willem
On Wednesday, November 6, 2013 at 5:44 PM, Claus Ibsen wrote:
> Hi
>
> It would be nice if we could log one time at INFO level all the xml
> features that was configured, so end users can see that.
> You could put all those into a List and then log th
Hi
It would be nice if we could log one time at INFO level all the xml
features that was configured, so end users can see that.
You could put all those into a List and then log that once. So the
logging don't get too verbose.
On Tue, Nov 5, 2013 at 9:50 AM, wrote:
> Updated
Github user lfoppiano closed the pull request at:
https://github.com/apache/camel/pull/8
GitHub user lfoppiano opened a pull request:
https://github.com/apache/camel/pull/8
New features for twitter-camel
Hello,
I have implemented a few new features that are available in the twitter4j
library and they are quite useful also in the camel twitter endpoint
dependency upgrades, the karaf features.xml does not
>validate anymore:
>
>http://svn.apache.org/viewvc?view=revision&revision=1396866
>
>The validation fails by camel-elasticsearch:
>
>~/dev/workspace/camel/platforms/karaf/features>mvn clean install
>-Pvalidate
>...
Hi
After the following dependency upgrades, the karaf features.xml does not
validate anymore:
http://svn.apache.org/viewvc?view=revision&revision=1396866
The validation fails by camel-elasticsearch:
~/dev/workspace/camel/platforms/karaf/features>mvn clean install -Pvalidate
...
[
Without this change, if I run
mvn clean install -Pvalidate
in plattform/karaf/features, I got
[WARNING] Failed to validate feature camel-websocket
[WARNING] No export found to match
org.eclipse.jetty.util.ssl;version="[7.5,8.2)" (imported by
mvn:org.apache.camel/camel-websocket/2.1
y feature from Karaf?
>> >
>> >
>> >
>> > On Wed, Oct 3, 2012 at 10:27 PM, wrote:
>> >> Author: cmueller
>> >> Date: Wed Oct 3 20:27:12 2012
>> >> New Revision: 1393744
>> >>
>> >> UR
rev=1393744&view=rev
> >> Log:
> >> fixed the feature.xml file
> >>
> >> Modified:
> >> camel/trunk/parent/pom.xml
> >> camel/trunk/platforms/karaf/fe
svn.apache.org/viewvc?rev=1393744&view=rev
>> Log:
>> fixed the feature.xml file
>>
>> Modified:
>> camel/trunk/parent/pom.xml
>> camel/trunk/platforms/karaf/features/src/main/resources/features.xml
>>
>> Modified: camel/trunk/parent/pom.
:27:12 2012
> New Revision: 1393744
>
> URL: http://svn.apache.org/viewvc?rev=1393744&view=rev
> Log:
> fixed the feature.xml file
>
> Modified:
> camel/trunk/parent/pom.xml
> camel/trunk/platforms/karaf/features/src/main/resources/features.xml
>
>
cused transformation rules, like you can do with the
> BPEL Assign activity. With XML payloads, I would love to copy, transfer,
> transform values from a source to an origin, without having to write an
> external resource (XSLT, XQuery, Velocity template, etc.). Take a look at
> the
cused transformation rules, like you can do with the
> BPEL Assign activity. With XML payloads, I would love to copy, transfer,
> transform values from a source to an origin, without having to write an
> external resource (XSLT, XQuery, Velocity template, etc.). Take a look at
> the
ds, I would love to copy, transfer,
transform values from a source to an origin, without having to write an
external resource (XSLT, XQuery, Velocity template, etc.). Take a look at
the data manipulation features in BPEL [1].
What do you think?
Also, something that's missing is running tran
Thanks a lot Claus!
I will study more the subject, and hopefully will not need to abuse your
availability further ;)
Thanks!
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5525681p5535112.html
Sent from the Camel
tions in some way, and
thus they can enlist into a TX manager.
For example a JMS consumer, or a JDBC producer etc.
> Thanks in advance
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5
n this subject?
Any help will be very useful!
Thanks in advance
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5525681p5534184.html
Sent from the Camel Development mailing list archive at Nabble.com.
y.
See this source for details
https://svn.apache.org/repos/asf/camel/trunk/components/camel-spring/src/main/java/org/apache/camel/spring/spi/TransactionErrorHandler.java
> Thanks a lot,
> Emanuele
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-features-and-
t to allow camel control it in a transactional way ?
Thanks a lot,
Emanuele
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-features-and-falling-back-to-Camel-components-tp5525681p5533706.html
Sent from the Camel Development mailing list archive at Nabble.com.
gt; Hello everyone,
> I am developing a RabbitMQ camel component starting from scratch, using the
> RabbitMQ java client as the only basis for the development.
>
> Aside from the RabbitMQ features I am exposing to the users as options in
> the route (e.g. ?concurrentConsumers),
>
>
Hello Bruno,
thanks for replying.
Since I am developing a camel component I though this was the best place to
ask.
It was not clear this is the ML only for "official" camel devs.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-features-and-falling-bac
oyota-europe.com
"E.Gherardini"
29/02/2012 19:09
Please respond to
dev@camel.apache.org
To
dev@camel.apache.org
cc
Subject
Camel features and falling-back to Camel components
Hello everyone,
I am developing a RabbitMQ camel component starting from scratch, using
the
RabbitMQ
Hello everyone,
I am developing a RabbitMQ camel component starting from scratch, using the
RabbitMQ java client as the only basis for the development.
Aside from the RabbitMQ features I am exposing to the users as options in
the route (e.g. ?concurrentConsumers),
I am wondering if there exist
w=rev
Log:
[CAMEL-4671] Reverting 1201768 (with permission from gnodet, the orinal
author) due to issues it is causing as discussed on dev list.
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/config.properties
camel/trunk/platforms/karaf/features/src/main/resources/fea
ing as discussed on dev list.
>
> Modified:
> camel/trunk/platforms/karaf/features/src/main/resources/config.properties
> camel/trunk/platforms/karaf/features/src/main/resources/features.xml
>
> Modified:
> camel/trunk/platforms/karaf/features/src/main/resources/config.properties
&
Hi Dan,
I tested camel-jibx, camel-hdfs, camel-atom, camel-rss, camel-jibx
features. It deploys without problem.
It looks good to me now and equivalent to that we have on Camel 2.8.x.
Regards
JB
On 12/27/2011 04:00 AM, Daniel Kulp wrote:
On Tuesday, December 27, 2011 12:14:09 AM Guillaume
the results were very promising. That would also mean that the
> >> exported package version is the default, so supporting 0.0 is a good
> >> thing imho.
> >>
> >> On Mon, Dec 26, 2011 at 20:59, Jean-Baptiste Onofré
> >>
> >> wrote:
> >>
t; > Hi Guillaume,
> >
> > first of all, merry Christmas to you and your family ;)
> >
> > Let me try to explain the current situation.
> >
> > In Camel, we have several features which depend on ServiceMix JAX-WS
> > Spec
> > (for instance, camel-s
Onofré
>> wrote:
>>>
>>> Hi Guillaume,
>>>
>>> first of all, merry Christmas to you and your family ;)
>>>
>>> Let me try to explain the current situation.
>>>
>>> In Camel, we have several features which depend on ServiceMix
version is the default, so supporting 0.0 is a good
thing imho.
On Mon, Dec 26, 2011 at 20:59, Jean-Baptiste Onofré wrote:
Hi Guillaume,
first of all, merry Christmas to you and your family ;)
Let me try to explain the current situation.
In Camel, we have several features which depend on Se
In Camel, we have several features which depend on ServiceMix JAX-WS Spec
> (for instance, camel-soap).
> The ServiceMix Specs explicitly define an import package like:
>
> javax.xml.bind;version="2.2.0"
>
> The jre package exports javax.xml.bind;version=0.0.0 by default.
&
Hi Guillaume,
first of all, merry Christmas to you and your family ;)
Let me try to explain the current situation.
In Camel, we have several features which depend on ServiceMix JAX-WS
Spec (for instance, camel-soap).
The ServiceMix Specs explicitly define an import package like
aniel Kulp wrote:
>
> The discussions around the entire xml-specs/jaxb/etc... stuff in the
features
> file has shown that this commit has caused a lot more problems than it's
> actually solving. Thus, I'm officially putting a -1 on this commit as
it's
> causing bre
I would like to see the changes from JB included. I run the test with Karaf
2.2.2, Karaf 2.2.4 and 2.2.5 and I could install all features without the
need to tune the jre.properties, the custom.properties or to install some
other features/bundles before. For the current Karaf (and SMX) versions I
Fully agree, it's what I did in my latest commits.
As I answered to Willem, I would prefer to have all features installable
out of the box and document the way we tune the jre.properties
(especially, starting from Karaf 2.2.5, we ship a jre.properties.cxf
commenting the packages).
The discussions around the entire xml-specs/jaxb/etc... stuff in the features
file has shown that this commit has caused a lot more problems than it's
actually solving. Thus, I'm officially putting a -1 on this commit as it's
causing breakages in other components, causes cast
Karaf. With the
start-level on the API's, when you restart, camel-core will then get
DIFFERENT
bundles than it did the first time.
Basically, the behavior is very indeterministic which, to me, will cause
issues trying to figure out what is going on when something goes wrong.
Dan
So it m
the first time.
Basically, the behavior is very indeterministic which, to me, will cause
issues trying to figure out what is going on when something goes wrong.
Dan
So it means that without these changes, these features will never work
even if we run using jre-1.6 profile.
I don't
..@apache.org wrote:
Author: jbonofre
Date: Fri Dec 23 15:56:36 2011
New Revision: 1222709
URL: http://svn.apache.org/viewvc?rev=1222709&view=rev
Log:
[CAMEL-4818] camel-hdfs and camel-soap reference xml-specs-api feature
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/fea
en you restart, camel-core will then get
DIFFERENT
bundles than it did the first time.
Basically, the behavior is very indeterministic which, to me, will cause
issues trying to figure out what is going on when something goes wrong.
Dan
So it means that without these changes, these features wi
Dan
So it means that without these changes, these features will never work
even if we run using jre-1.6 profile.
I don't understand the previous change to be honest.
Regards
JB
On 12/24/2011 02:46 PM, Daniel Kulp wrote:
On Saturday, December 24, 2011 4:29:53 PM Willem Jiang wrote:
-1 for
Basically, the behavior is very indeterministic which, to me, will cause
issues trying to figure out what is going on when something goes wrong.
Dan
>
> So it means that without these changes, these features will never work
> even if we run using jre-1.6 profile.
>
> I do
Hi Dan,
did you see my latest e-mail on this thread ?
I don't see any problem, as camel-hdfs or camel-soap reference
ServiceMix Specs JAXWS, which reference JAXB 2.2
(javax.xml.bind*;version=2.2 and not just javax.xml.bind*).
So it means that without these changes, these features will
rev
> > Log:
> > [CAMEL-4818] camel-hdfs and camel-soap reference xml-specs-api feature
> >
> > Modified:
> > camel/trunk/platforms/karaf/features/src/main/resources/featur
> > es.xml
> >
> > Modified:
> > camel/trunk/platforms/karaf/
-4818] camel-hdfs and camel-soap reference xml-specs-api feature
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/features.xml
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/features.xml
URL:
http://svn.apache.org/viewvc/camel/trunk/platforms/karaf/features/src/main
Really I don't understand.
camel-hdfs and camel-soap features don't work out of the box EVEN using
a JRE 1.6 profile (because the version mismatch): it's exactly the test
that I did on a Karaf 2.2.4, using a JDK 1.6 with jre-1.6 profile.
For me, it's worse to have c
p;view=rev
Log:
[CAMEL-4818] camel-hdfs and camel-soap now reference xml-specs-api
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resources/features.xml
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resources/features.xml
URL:
http://svn.apache.or
camel/trunk/platforms/karaf/features/src/main/resources/features.xml
Modified: camel/trunk/platforms/karaf/features/src/main/resources/features.xml
URL:
http://svn.apache.org/viewvc/camel/trunk/platforms/karaf/features/src/main/resources/features.xml?rev=1222709&r1=1222708&r2=
apache.org wrote:
Author: jbonofre
Date: Fri Dec 23 16:20:23 2011
New Revision: 1222723
URL: http://svn.apache.org/viewvc?rev=1222723&view=rev
Log:
[CAMEL-4818] camel-hdfs and camel-soap now reference xml-specs-api
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resource
wrote:
Author: jbonofre
Date: Fri Dec 23 16:20:23 2011
New Revision: 1222723
URL: http://svn.apache.org/viewvc?rev=1222723&view=rev
Log:
[CAMEL-4818] camel-hdfs and camel-soap now reference xml-specs-api
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resources/fea
e.org/viewvc?rev=1222723&view=rev
Log:
[CAMEL-4818] camel-hdfs and camel-soap now reference xml-specs-api
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resources/features.xml
Modified:
camel/branches/camel-2.8.x/platforms/karaf/features/src/main/resources/feature
2011
>>> New Revision: 1213320
>>>
>>> URL:
>>> http://svn.apache.org/viewvc?**rev=1213320&view=rev<http://svn.apache.org/viewvc?rev=1213320&view=rev>
>>> Log:
>>> CAMEL-4675: Allign the version number for qpid we use in our c
mel/trunk/parent/pom.xml
camel/trunk/platforms/karaf/features/pom.xml
Modified: camel/trunk/parent/pom.xml
URL:
http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?rev=1213320&r1=1213319&r2=1213320&view=diff
AMEL-4675: Allign the version number for qpid we use in our component and in
our feature file
Modified:
camel/trunk/parent/pom.xml
camel/trunk/platforms/karaf/features/pom.xml
Modified: camel/trunk/parent/pom.xml
URL:
http://svn.apache.org/viewvc/camel/trunk/parent/pom.xml?rev=1
d:
>camel/trunk/parent/pom.xml
>camel/trunk/platforms/karaf/features/pom.xml
>camel/trunk/platforms/karaf/features/src/main/resources/features.xml
>
> Modified: camel/trunk/parent/pom.xml
> URL:
> http://svn.apache.org/viewvc/camel/trunk/par
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/features.xml
Modified:
camel/trunk/platforms/karaf/features/src/main/resources/features.xml URL:
http://svn.apache.org/viewvc/camel/trunk/platforms/karaf/features/src/main/
resources/features.xml?rev=1202205&r1=1202204&r2=
ature into apache-camel
>
> Modified:
> camel/trunk/platforms/karaf/features/src/main/resources/features.xml
>
> Modified:
> camel/trunk/platforms/karaf/features/src/main/resources/features.xml URL:
> http://svn.apache.org/viewvc/camel/trunk/platforms/karaf/
Well I'm glad I'm not the only one.
The disparity between camel and cxf was the biggest issue, since camel
overrides the cxf feature with other versions.
In the customer case I resolved it with using karaf features + camel features,
that at least got the cxf bundles in cleanly - b
On Wednesday, October 19, 2011 10:13:23 AM Gert Vanthienen wrote:
> L.S.,
>
> Yeah, we are moving in the right direction there, so nice work! One thing I
> bumped into while doing a bit of a refactoring of the servicemix features
> codebase, was the fact that some features descri
nd in all (karaf, cxf, servicemix, activemq)
features descriptors we use to fix this problem. Another option could be to
use a single OBR in-memory repository for resolving all boot features and
only then switch to the per-feature resolver implementation we are currently
using. Perhaps the latter is
L.S.,
Yeah, we are moving in the right direction there, so nice work! One thing I
bumped into while doing a bit of a refactoring of the servicemix features
codebase, was the fact that some features descriptors contain a reference to
another one, e.g. the camel features descriptor refers to the
l Kulp wrote:
>>
>>> On Friday, October 14, 2011 11:58:26 PM Johan Edstrom wrote:
>>>> Hey,
>>>>
>>>> Just poking around in the features, and yes I cross post this -
>>>>
>>>> I know there has been work going on with regards
> On Oct 15, 2011, at 12:26 AM, Daniel Kulp wrote:
>
>> On Friday, October 14, 2011 11:58:26 PM Johan Edstrom wrote:
>>> Hey,
>>>
>>> Just poking around in the features, and yes I cross post this -
>>>
>>> I know there has been work going on wi
natype OBR repo last week, that would help.
/je
On Oct 15, 2011, at 12:26 AM, Daniel Kulp wrote:
> On Friday, October 14, 2011 11:58:26 PM Johan Edstrom wrote:
>> Hey,
>>
>> Just poking around in the features, and yes I cross post this -
>>
>> I know there has
On Friday, October 14, 2011 11:58:26 PM Johan Edstrom wrote:
> Hey,
>
> Just poking around in the features, and yes I cross post this -
>
> I know there has been work going on with regards to creating a sane default
> set of features but currently the CXF features in 2.4
Hey,
Just poking around in the features, and yes I cross post this -
I know there has been work going on with regards to creating a sane default set
of features
but currently the CXF features in 2.4.2 (I think it was) uses spring 3.0.6, the
karaf features 3.0.5
and the camel features
[
https://issues.apache.org/jira/browse/CAMEL-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré resolved CAMEL-4415.
-
Resolution: Fixed
> Use Karaf new spring featu
sion 1178331.
> Use Karaf new spring features
> -
>
> Key: CAMEL-4415
> URL: https://issues.apache.org/jira/browse/CAMEL-4415
> Project: Camel
> Issue Type: Improvement
>
[
https://issues.apache.org/jira/browse/CAMEL-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré reopened CAMEL-4415:
-
> Use Karaf new spring featu
[
https://issues.apache.org/jira/browse/CAMEL-4415?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jean-Baptiste Onofré updated CAMEL-4415:
Fix Version/s: 2.8.2
> Use Karaf new spring featu
1 - 100 of 343 matches
Mail list logo
