camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hadrian Zbarcea <hzbar...@gmail.com>
Subject Re: Do Apache Camel needs a SAP integration?
Date Fri, 16 Mar 2012 01:44:38 GMT
I don't think hosting at the asf is an option (if that's what you meant) 
but Romain's proposal works and is imho the best option.

Hadrian


On 03/15/2012 07:52 PM, Christian Müller wrote:
> I opened the JIRA to track this [1].
> I will also check with legal what possibilities we have to host the needed
> dependency but not to include it. I would like to run/build the component
> as all others and use mocks to test it.
>
> [1] https://issues.apache.org/jira/browse/CAMEL-5094
>
> Best,
> Christian
>
> 2012/3/6 Björn Bength<bjorn.bength@gmail.com>
>
>> Hi
>>
>> I forgot to open a JIRA for this.
>> But what do you mean? No, we can't add the dependencies to a repo, but
>> we can refer to a doc that describes what to do to add it to one's
>> local repo.
>> Maybe we can't include the component into camel-extra and have people
>> build the entire stack of camel-extra components without messing with
>> these jars, but there has to be a way of dealing with this sort of
>> problems too, right?
>>
>> camel-manual-extra project :-)
>> Or just use the project camel-hibersap from github and follow the
>> instructions.
>>
>> regards.
>> Björn
>>
>>
>> On Mon, Mar 5, 2012 at 11:47 PM, Romain Manni-Bucau
>> <rmannibucau@gmail.com>  wrote:
>>> Hi,
>>>
>>> can't it be added to the google project creating a repo in the source
>>> repository?
>>>
>>> - Romain
>>>
>>>
>>> 2012/3/5 Christian Müller<christian.mueller@gmail.com>
>>>
>>>> I think the problem is to add the dependency "org.sap/sap-jco/x.y.z" to
>> an
>>>> ASF maven repository. Without it, we cannot build this component.
>> Because
>>>> of this, I see no way to host this component at camel-extra. :-(
>>>>
>>>> Best,
>>>> Christian
>>>>
>>>> On Fri, Jan 20, 2012 at 7:22 PM, Christian Müller<
>>>> christian.mueller@gmail.com>  wrote:
>>>>
>>>>> +1
>>>>> This will make a few things easier for us and for our users.
>>>>> Of course, we can host this component in camel-extra on googlecode,
>> but
>>>> we
>>>>> often ignore/forget these components (the last version is 2.8.0). And
>> I
>>>>> think many of our users don't know that we also host some components
>>>>> because of license reasons on camel-extra.
>>>>>
>>>>> I will checkout the code from github and play with it a bit...
>>>>>
>>>>> @Björn: If you are the owner of this contribution, could you please
>> open
>>>> a
>>>>> JIRA for this new component and attach it (don't forget to grant the
>>>> Apache
>>>>> license). Than we could put it into camel-extra and start to work to
>>>>> improve this component. And if Hibersap is licensed with a compatible
>>>>> license, we can move it into our repo at Apache.
>>>>>
>>>>> Best,
>>>>> Christian
>>>>>
>>>>> On Fri, Jan 20, 2012 at 11:39 AM, Erker, Carsten<
>>>>> Carsten.Erker@akquinet.de>  wrote:
>>>>>
>>>>>> Hi Christian,
>>>>>>
>>>>>> yes, a colleague who is Apache member just explained it to me.
>>>>>>
>>>>>> We are discussing about switching to ASL 2.0 with the next version.
>>>>>>
>>>>>> Regards,
>>>>>> Carsten
>>>>>>
>>>>>>
>>>>>>
>>>>>> Am 20.01.2012 um 10:36 schrieb Christian Schneider:
>>>>>>
>>>>>>> Hi Carsten,
>>>>>>>
>>>>>>> you migth want to take a look at the Apache license policies:
>>>>>>> http://www.apache.org/legal/3party.html
>>>>>>>
>>>>>>> LGPL is listed as excluded so it may not be used as a dependency
>> of an
>>>>>> apache product (as far as I understand).
>>>>>>> I am not sure why it can´t be used but I guess some lawyer has
>> helped
>>>>>> with that policy.
>>>>>>>
>>>>>>> Christian
>>>>>>>
>>>>>>>
>>>>>>> Am 20.01.2012 09:27, schrieb cerker:
>>>>>>>> Björn, thanks a lot for sharing your camel-hibersap component.
I
>> only
>>>>>> just
>>>>>>>> started playing around with camel and liked it very much.
Now
>> there
>>>> is
>>>>>> a
>>>>>>>> good reason to take a deeper look.
>>>>>>>>
>>>>>>>> It's good to hear that Hibersap helped you with your project.
>>>>>> Regarding the
>>>>>>>> license, I think there should be no problems to combine libraries
>>>> that
>>>>>> are
>>>>>>>> under the Apache license and ones under LGPL (at least in
their
>>>> current
>>>>>>>> versions). We initially liked the idea of a copyleft license
and
>> LGPL
>>>>>> is the
>>>>>>>> one most widely used. After all, I am not a lawyer and the
big
>>>>>> disadvantage
>>>>>>>> of LGPL is that nobody seems to fully understand it and things
are
>>>>>> open to
>>>>>>>> interpretation. Anyway, I'll have a talk with some people
in my
>>>>>> company who
>>>>>>>> have a deeper understanding of OS licenses and we'll rethink
the
>>>>>>>> licensing....
>>>>>>>>
>>>>>>>> If you got any questions feel free to contact me via email
or use
>> the
>>>>>>>> Hibersap forums or issue tracker on Sourceforge.
>>>>>>>>
>>>>>>>> Best Regards,
>>>>>>>> Carsten
>>>>>>>> (Founder of the Hibersap project)
>>>>>>>>
>>>>>>>> -
>>>>>>>
>>>>>>> --
>>>>>>> Christian Schneider
>>>>>>> http://www.liquid-reality.de
>>>>>>>
>>>>>>> Open Source Architect
>>>>>>> Talend Application Integration Division http://www.talend.com
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>
>

-- 
Hadrian Zbarcea
Principal Software Architect
Talend, Inc
http://coders.talend.com/
http://camelbot.blogspot.com/

Mime
View raw message