Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orbit-dev] Modifying source of a 3rd party library

This whole topic is interesting. From a historical perspective (that's why you keep us old guys around remember) Orbit was never envisioned to actually compile anything. The scenario actually makes some sense if the changes are: actually required required, of general use, not disruptive to other uses of the library and not in the originators code in time for the consuming project's release. If these conditions are not met then the changes likely should happen in an isolated way in the consuming project. Either way, seems to me that the bundle should be given an org.eclipse name if the real content is being modified (as per Markus' suggestion)

Jeff

Markus Alexander Kuppe wrote:
Why not change the bundle symbolic naming? Nowadays people should import
packages rather than require bundles anyway. ;-o



Back to the top