Grokbase Groups Camel dev August 2015
FAQ
Dan,

Thanks for updating snappy on commit 1234e0a2d.

What's your call? Shall we cancel this release and start a new one? If we
cancelled attempt #1 due to a freemarker OSGi dep issue, I think this issue
deserves the same treatment. Actually, since it affects more components,
all the more reason to cancel it.

I know it can be quite a bit of work to initiate a new take, so I'll be
happy to take the release manager hat this weekend if you'd like. I just
need to set up my keys. If you guys can help me out (cross-signing and
stuff), it would be great.

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Aug 13, 2015 at 8:33 PM, Daniel Kulp wrote:


Hmm… none of these are a regression from 2.15.2 as 2.15.2 fails in the
same way. :(

A majority of the (!) things can be fixed by updating to snappy-java
1.1.1.7.

The camel-cxf issue is a bug in Karaf 2.4 (fixed on Karaf master for 4.0.1
and I think for a future 2.4.x). I think if you edit the jre.properties to
stick the javax.activation to version 1.0 this will be OK.

camel-jetty9 will never work on Karaf 2.x (or 3.x) as those versions of
Karaf are based on Jetty 8.

Dan


On Aug 13, 2015, at 2:06 PM, Raul Kripalani wrote:

Tried installing all features in Karaf 2.4.3 with the following ones
failing (legend for symbol in brackets below):

* (!) camel-avro
* (c) camel-cxf (only in presence of some other feature I haven't
determined - ok when installed on an empty container)
* (!) camel-hazelcast
* (!) camel-hbase
* (!) camel-hdfs2
* (!) camel-infinispan
* (!) camel-jetty9
* (c) camel-linkedin
* (e) camel-optaplanner
* (!) camel-sip
* (!) camel-spark-rest
* (!) camel-spring-security
* (c) camel-swagger
* (!) camel-vertx

Full output available here: [1]. I haven't stopped to analyse each failure
in detail. But with a quick inspection I have triaged these failures in 3
categories:

(!) package resolution problem or activator problem – major
(c) conflict with another bundle – minor
(e) environment configuration (e.g. needing to export additional packages
from JRE) – trivial

At this point I am tempted to -1 the release, but I'd like to have your
opinion first.

[1] https://gist.github.com/raulk/7eeed09d4a7f1780d56a

Regards,

*Raúl Kripalani*
Apache Camel PMC Member & Committer | Enterprise Architect, Open Source
Integration specialist
http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani
http://blog.raulkr.net | twitter: @raulvk
On Thu, Aug 13, 2015 at 5:16 PM, Daniel Kulp wrote:

This is a vote to release Apache Camel 2.15.3. It’s been quite a while
since 2.15.2 and with lots of bugs fixed, it would be great to get it
out
there. This second attempt fixes the problem with free marker
component
that prevents it from running in Karaf/OSGi.


Staging area:
https://repository.apache.org/content/repositories/orgapachecamel-1033/

Tag:
https://git-wip-us.apache.org/repos/asf?p=camel.git;a=tag;h=627c12eaf6ca457d3ebb3183d8b3c9063703c57b
Fixed issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12311211&version=12332259

Here is my +1. Vote will be open for at least 72h.


--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com

Search Discussions

Discussion Posts

Previous

Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 9 | next ›
Discussion Overview
groupdev @
categoriescamel
postedAug 13, '15 at 4:16p
activeAug 14, '15 at 6:09p
posts9
users2
websitecamel.apache.org

2 users in discussion

Raul Kripalani: 5 posts Daniel Kulp: 4 posts

People

Translate

site design / logo © 2022 Grokbase