[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orbit-dev] Modifying third-party projects
|
Hi Lazar,
Am 21.11.2012 15:42, schrieb Kirchev, Lazar:
What is the correct approach here? Add the fixed in another version? Or
in a new project? Or not adding at all to Orbit until a version
containing all the fixes gets released officially from the third party –
in this case the modified bundles could safely reside in a Virgo project
repository?
We have a similar issue for MongoDB. In this case we *have to* publish a
modified version of the library for IP reasons. According to the naming
policy I named the bundle org.eclipse.orbit.mongodb to indicate that
this is a custom bundle and not the official project library. I kept the
bundle version the same as the original version well as the version of
the exported packages.
The modified source is checked in to Orbit as well together with the
modified binaries and published as part of the source bundle.
-Gunnar
--
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx
http://wagenknecht.org/
