camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From deckerego <>
Subject Re: Writing own Camel Components
Date Thu, 10 Nov 2011 18:43:33 GMT
After a good deal of discussion it looks like the best thing to do is to
release this under the Mozilla Public License v2.0 that's due to be released
this month (at least according to the mailing list). The decision isn't
necessarily based on the project being incompatible with the Apache License
2 (RabbitMQ appears to be okay as a binary exclusion) but more on the
feedback spurred by this post. 

I'll refactor the project (i.e. package names) to draw a greater distinction
between this project and an ASF sponsored project, then re-push the project
to GitHub.

deckerego wrote:
> Your read on the license mirrors my own. I too understood that the
> exclusions referred to packaging within Apache /projects/ and not
> necessarily software that is not part of a project but licensed under the
> Apache License 2.0. In this case the project was released under the Apache
> License 2.0 but was not part of an Apache Software Foundation project, so
> the guidance specified within
> would not apply since it governs ASF projects.
> Ultimately I may have the camel-spring-amqp reviewed for re-release under
> MPL 1.1. VMware seems to enjoy releasing under that license at least.
> Jim Apperly wrote:
>> There seems to be a little confusion about what the ASF permits re:
>> licensing.  
>> The ASF does explicitly forbid packaging ASL2 code with third party code
>> licensed under what they call "Category X" licenses. This includes things
>> like the GPL but definitely not the MPL.
>> MPL1.1 - under which RabbitMQ is licensed - falls into ASF's "Category B"
>> list. Software under these licenses "may be included in binary form
>> within an Apache product if the inclusion is appropriately labeled".  The
>> following link has more:
>> It may also be worth pointing out that using the ASL2 does not require
>> you to contribute code to the ASF, therefore you can safely ignore them.

View this message in context:
Sent from the Camel - Users mailing list archive at

View raw message