[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-ocl.dev] Fwd: [cross-project-issues-dev] Status and outl ook for "Final +3 exception builds"
|
Ah, but the reason for retagging and re-releasing is that, AFAIK, the feature qualifiers are based on the tag in the map file. Unless you're using a combination of tag and timestamp to produce the JAR versions, in which case the specific (complete) JAR version ought to be referenced from the Helios build file.
Bottom line is, if one of the bundles has changed (and has a different JAR version), the containing feature(s) need(s) to change (and have a different JAR version) so that the newer bundle is picked up during installation...
Kenn
On Wed, Jun 16, 2010 at 1:54 PM, Ed Willink
<ed@xxxxxxxxxxxxx> wrote:
Hi
I think tagging is a red herring. The master feature has not changed since 3rd May, so accessing the same file versions by a different tag should not matter, unless there is a transitive tagging requirement that the master feature tag must be more recent than all features that it includes ...
a) You're right; there is a tagging problem. The master feature tag managed to go backwards immediately after RC2, as a result of a misguiged attempt by me to help when Alex appeared not to be getting RC2 out. Somehow the tooling has not changed the master feature for RC3, RC4 or 'RC5'.
Ed
