Thanks, Kenn. Please do not apologise - that's all my fault.
I am using releng tools plugin which helps to do the correct tagging based on the changes in the repository. It didn't retag the feature though retagged the included bundle - well, I relied on it. I agree that if installed into the same platform the feature with the same version shouldn't be picked up but this was not the case...
I think I got too happy to have produced the final R-build on Monday night that I forgot to do the last step - let Helios know about it... I should have been more careful...
Thanks, Alex. I just installed the latest OCL bits from the release repository and have confirmed myself that the newer OCL parser example (3.0.0.v201006150300) does in fact get picked up. Sorry for all the unnecessary concern that I may have raised. It's hard to know whether something's wrong when each project has a different build system and associated conventions... Hopefully these differences will go away once we've all switched to Buckminster. ;)
Ed, please do not retag or rebuild. I have published the correct final R-build on Monday (it is hidden now at the downloads page). However, I forgot to change the update site URL in the mdt-ocl.build file - so Helios build took our RC4...
I have fixed it - the correct OCL build should be included since now. May I request a Helios rebuild?
My apologies for the inconvenience.
- Alex.
On Wed, Jun 16, 2010 at 10:33 PM, Ed Willink <ed@xxxxxxxxxxxxx> wrote:
Hi Kenn
Ok, so I was right to just retag always when I did an intermediate
build.
I'll retag and rebuild so that we actually create a new version.
Alex is now responding so perhaps in an hour he can do an R and in 2
hours we can contribute.
Ed
On 16/06/2010 19:17, Kenn Hussey wrote:
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'.
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 9.0.829 / Virus Database: 271.1.1/2941 - Release Date: 06/16/10 07:35:00
