Re: [incubation] wrap binaries into a plugin

["Alois Z." <alois.zoitl@xxxxxx>]

Sorry for hijacking this thread a bit bit this raised also some questions how to handle third-party dependencies for non Java/Osgi  based projects.

 

For example in 4diac FORTE we work with 5 differentn operating systems (the 6th is in the making) and several libraries, for example communication but also IoT device vendor speficif libraries (e.g., I/O access).

 

How do we need to handle these?

 

For IoT projects like 4diac abstracting these libraries is a key USP for our users and therfore very important for us.

 

Cheers,

Alois

 

Gesendet: Freitag, 24. Juni 2016 um 17:18 Uhr
Von: "Wayne Beaton" <wayne@xxxxxxxxxxx>
An: incubation@xxxxxxxxxxx
Betreff: 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)

 

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
incubation@xxxxxxxxxxx
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 incubation@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/incubation