Subject, of course, to the Eclipse IP Due Diligence process, you can
distribute the built code in whatever manner makes the best technical sense.
HTH,
Wayne
On 27/06/16 04:28 AM, LORENZO Vincent wrote:
HI Wayne,
Thank you for your answer. I didn’t include EPL, because I already
know, that it will not choosen by the owner of the project, but of
course, I agree it would be the best way for us.
In our case, we are working with C++ and we use an external C++
library, so it will not be a .jar.
Regards,
--
Vincent Lorenzo
*De :*[email protected]
[mailto:[email protected]] *De la part de* Wayne Beaton
*Envoyé :* vendredi 24 juin 2016 17:18
*À :* [email protected]
*Objet :* Re: [incubation] wrap binaries into a plugin
EPL is certainly our preference for dual licensing; I'm curious to
know why it's not included on the list of potential selections.
The preferred means of distributing a third-party library in an OSGi
context is to turn the JAR into a standalone bundle that can be
independently managed, and easily leveraged and shared by multiple
consumers. The Orbit project mailing list (orbit-dev) is a good place
to find advice on this topic. You might also be able to get some help
from the EBR project; EBR provides templates and tools for creating
bundles from third-party libraries.
If there are technical limitations that make it impossible for the
library to be a standalone bundle, embedding a third-party JAR is
technically possible.
Note that the Eclipse Planning Council adds some restrictions in this
area for projects that participate in the simultaneous releases.
HTH,
Wayne
On 24/06/16 09:19 AM, LORENZO Vincent wrote:
Hello everybody,
I’m working with a C++ library using the GPL license. The
owner of the project seems agree to change its license (or dual
licensing its project) which a license allowed by Eclipse :
•Apache Software License 1.1
•Apache Software License 2.0
•W3C Software License
•Common Public License Version 1.0
•IBM Public License 1.0
•Mozilla Public License Version 1.1
•Common Development and Distribution
License (CDDL) Version 1.0
•GNU Free Documentation License Version 1.3
•BSD
•MIT
(found on page 2 of this document :
https://eclipse.org/legal/EclipseLegalProcessPoster.pdf
<https://eclipse.org/legal/EclipseLegalProcessPoster.pdf>)
So, I would like to know if I can embed the library as binaries
into a plugin if the license is allowed by Eclipse ?
In addition, do you know if dual licensing is OK (GPL and an
others license ? )
I know in some case we could push used libraries into the Orbit
project, but I would like to avoid this way.
Regards,
--
Vincent LORENZO
01-69-08-17-24
CEA Saclay Nano-INNOV
Institut CARNOT CEA LIST
DILS/LISE
Point Courrier n° 174
91 191 Gif sur Yvette CEDEX
_______________________________________________
incubation mailing list
[email protected] <mailto:[email protected]>
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
--
Wayne Beaton
@waynebeaton
The Eclipse Foundation
_______________________________________________
incubation mailing list
[email protected]
To change your delivery options, retrieve your password, or unsubscribe from
this list, visit
https://dev.eclipse.org/mailman/listinfo/incubation
