Bugzilla – Full Text Bug Listing
| Summary: | Tests run with Equinox 3.5 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] Virgo | Reporter: | Hristo Iliev <hsiliev> | ||||
| Component: | virgo-build | Assignee: | Project Inbox <virgo-inbox> | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P3 | CC: | eclipse, glyn.normington, zteve.powell | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
If there is a way to parametrize the Equinox version that would be a good solution. I'm now experimenting with quality.xml and trying to remove the hardcoded version from there. If we remove revision from the osgi.init this will result in always using the latest integration version. I'm not sure that's a solution at all. Created attachment 181498 [details]
Changed OSGI version (3.6.1.R36x_v20100806)
Hristo, This version is only used in quality.xml in the target 'osgi.init' This target is only used in target 'osgi-validate'. No virgo builds use this target, it is used in EBR updates. We ought to remove it. In any case, no build target will pull in the old version of org.eclipse.osgi.version (and if you look in the ivy_cache you will never see it brought in by a clean build). So this is not an issue, and need not be fixed. The tests are not running against an old version. Indeed no 3.5 version is present in the cache. I just started a build to verify this. |
Build Identifier: I noticed in common.properties: org.eclipse.osgi.version=3.5.0.v20090311-1300 The value is used in quality.xml in the osgi.init target: <ivy:cachepath resolveId="equinox.classpath" pathid="equinox.classpath" organisation="org.eclipse.osgi" module="org.eclipse.osgi" revision="${org.eclipse.osgi.version}" type="jar" inline="true" log="download-only"/> This would mean that the tests are running on 3.5 instead of 3.6. Reproducible: Always