Hi
The old 1.7 version is actually wrong in its pom.xml file. If you take
a note you can see the native drivers are the older 1.5 version which
is totally wrong.
org.fusesource.leveldbjni:leveldbjni-linux32:jar:1.5:compile
The intent is also these native drivers has scope provided. So you as
an
Would this have gone in had it been a regular git hub project?
That's really the only question you need to ask yourself, right?
Sent from my pressure cooker.
On Oct 18, 2013, at 18:25, Christian Müller wrote:
> I'm sure you know the project much better than me, but if you have a look
> at the d
I'm sure you know the project much better than me, but if you have a look
at the dependency tree for camel-leveldb 2.12.1:
[INFO] org.apache.camel:camel-leveldb:bundle:2.12.1
...
[INFO] +- org.fusesource.leveldbjni:leveldbjni-all:jar:1.7:compile
[INFO] | +- org.fusesource.leveldbjni:leveldbjni-os
Not every project has 3 digits for their versions. Some have only 2.
And these projects may do bug fix releases where upgrading is safe/compatible.
So when a 2 digit project does a release, then it can be a bug fix
release like leveldb 1.7 to 1.8 is.
For example you can try
http://vdiff.notsoclev
Is this minor dependency upgrade in a Camel micro release also because of
an issue with Leveldb in Camel 2.12.1? Do we have an issue for this?
Best,
Christian
-
Software Integration Specialist
Apache Member
V.P. Apache Camel | Apache Camel PMC Member | Apache Camel committer
Apa
