Just a followup…
The flatpack folks are going to try and push a 3.4.3 release this weekend with
the imports marked optional.Early next week, I’ll update Camel on master
and 2.15.x. Since CXF patches should be released by then, I’ll update that as
well. Is there anything else anyone n
+1, if it's possible in short term.
If not, I agree with Dan's proposal to exclude the dependency from the
pom.xml and remove if from the feature file. We should add a not to the
feature file how they can install the missing bundle and why we don't
install it by default.
Best,
Christian
On Wed, Jul 29, 2015 at 2:23 PM, Daniel Kulp wrote:
>
>> On Jul 29, 2015, at 6:44 AM, Claus Ibsen wrote:
>>
>> Why cant the SMX team release a fixed bundle in a fast time? Then
>> that can easily make it for upcoming Camel releases.
>
> Don’t know. Would need to check.
>
> Another option is to
> On Jul 29, 2015, at 6:44 AM, Claus Ibsen wrote:
>
> Why cant the SMX team release a fixed bundle in a fast time? Then
> that can easily make it for upcoming Camel releases.
Don’t know. Would need to check.
Another option is to drop to Flatpack 3.2 as there are smx bundles for that
already
Why cant the SMX team release a fixed bundle in a fast time? Then
that can easily make it for upcoming Camel releases.
On Tue, Jul 28, 2015 at 8:03 PM, Daniel Kulp wrote:
> camel-flatpack currently pulls in jexcelapi. Unfortunately, that library is
> LGPL and thus is not something we can h
Hi,
you could raise an issue on https://github.com/Appendium/flatpack with a note
for 3.4.X branch.
-Original Message-
From: Daniel Kulp [mailto:dk...@apache.org]
Sent: Tuesday, July 28, 2015 8:04 PM
To: dev@camel.apache.org
Subject: camel-flatpack license issue
camel-flatpack
camel-flatpack currently pulls in jexcelapi. Unfortunately, that library is
LGPL and thus is not something we can have as part of out default builds of
components and stuff. I’ve excluded that dep in the pom and all of our tests
pass. However, the flatpack bundle lists those imports as requ
