|Re: [cross-project-issues-dev] Bundle Version Management
On 17/08/2012 3:52 PM, John Arthorne wrote:
Ed Merks <ed.merks@xxxxxxxxx> wrote on 08/17/2012 08:49:16 AM:Well, we specify exactly the feature ID for the license so it ought not to ever change for free. Also, with our version tool, if the license feature changes, its version number must be changed, and once that's change, every feature that includes it must change its version number too, in a way that's consistent with the version change in the license, i.e., if the license change is a micro change, the including features need a micro increment, if it's a minor change, the including features need a minor increment.
If an EPL v2.0 came out, we couldn't have projects automatically picking it up.No, we'd have to change each of our license features, i.e., the one for EMF the EMF project's features.
Also licenses tend to evolve differently than other dependencies. When they change, you generally want to change every singe feature at once so a search & replace is very easy to do.The versioning tool would tell you that other features need increment and why, i.e., because of the increment of a particular dependency.
Having said all that, you could use 0.0.0 if you were very careful about ensuring only the right license was available at build time.I imagine every project has their own specific license feature so as long as my build extracts the license feature along with the rest of the source, it's inherently consistent...
I see. That's a corner case that's possible. I imagine most avoid this by controlling carefully what's available at build time...
Back to the top