[
https://issues.apache.org/jira/browse/CAMEL-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006850#comment-13006850
]
Jean-Baptiste Onofré commented on CAMEL-3784:
-
Hi guys, this Jira is not dupli
Hi Hadrian,
did you rollback the 2.7.0 release ?
On the trunk, I still have 2.8-SNAPSHOT version, so I guess it's not
already done.
I have some patches in preparation but I would like to generate the
patches on the right version :)
Thanks
Regards
JB
On 03/11/2011 11:55 AM, Hadrian Zbarcea
[
https://issues.apache.org/jira/browse/CAMEL-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006856#comment-13006856
]
Willem Jiang commented on CAMEL-3784:
-
No, this issue is not related to the feature fi
[
https://issues.apache.org/jira/browse/CAMEL-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006860#comment-13006860
]
Jean-Baptiste Onofré commented on CAMEL-3784:
-
I'm not talking about the featu
[
https://issues.apache.org/jira/browse/CAMEL-3784?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006866#comment-13006866
]
Willem Jiang commented on CAMEL-3784:
-
We can't upgrade Jetty to 7.3.1 until a new ver
Hi all,
FYI, I fixed KARAF-505 this morning.
Karaf 2.1.5 will support the resolver="(obr)" notation.
Regards
JB
On 03/11/2011 07:07 PM, Hadrian Zbarcea wrote:
We knew this patch will go in, now or 2.8.0 which meant that the compatibility
with karaf 2.1.x will be broken at some point. There i
[
https://issues.apache.org/jira/browse/CAMEL-3767?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Claus Ibsen closed CAMEL-3767.
--
Resolution: Duplicate
Assignee: Claus Ibsen
Duplicate of CAMEL-3784
> Upgrade to Jetty 7.3.1
> -
[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006905#comment-13006905
]
Willem Jiang commented on CAMEL-3763:
-
I just ran the itest-osgi-karaf with the latest
I just ran the itest-osgi-karaf with the latest patch, and found current
PaxExam doesn't support to load two features with different versions or
load the features from other features file, so current camel osgi
integration tests doesn't work with the patched camel-feature.
I'm not sure how the
Hi Willem,
thanks for your tests.
I'm gonna check your issue (I will discuss with you on IRC around that).
Regards
JB
On 03/15/2011 02:18 PM, Willem Jiang wrote:
I just ran the itest-osgi-karaf with the latest patch, and found current
PaxExam doesn't support to load two features with differen
[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006912#comment-13006912
]
Willem Jiang commented on CAMEL-3763:
-
I just added
mvn:org.apache.karaf.assemblies.f
[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006916#comment-13006916
]
Jean-Baptiste Onofré commented on CAMEL-3763:
-
You don't need the repository t
[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006912#comment-13006912
]
Willem Jiang edited comment on CAMEL-3763 at 3/15/11 1:48 PM:
--
[
https://issues.apache.org/jira/browse/CAMEL-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006922#comment-13006922
]
Willem Jiang commented on CAMEL-3763:
-
@JB,
As I can't run the osgi integration test o
Hey Willem, JB,
If I understand you correctly this problem should only affect 2.2.x
branch but not the master. The problem should be, AFAIK that we use
pax-exam 1.2.3 in karaf-2.2 which uses an old version of karaf. I'll
upgrade 2.2.x to exam 1.2.4. Can you please check if this fixes your
problems
Hello dev!
I would like to get an advice from your for [1].
I would prefer to implement the AWS SNS component to "only" provide a
producer (which sends notification to the AWS SNS topic).
In my opinion, the user should be responsible to configure the subscription
for this topic (outside of Camel
Hi Andreas,
I updated the camel itest-osgi-karaf to use Pax-Exam 1.2.4, it looks
like current pax-exam doesn't support the new features of Karaf-2.2.0.
As karaf stand feature has more than on Spring feature, it's hard to let
the pax-exam to tell which version of feature it should load. So the
Hi Christian,
It looks like the subscription can be implemented as a connector.
In this way user could configure the connector as they want and your SNS
component could be free to this kind detail message.
If you take a look at camel-jms component, it resolve the same question
by setting the
18 matches
Mail list logo