| Re: [mat-dev] MAT for Indigo |
I have made the MAT contribution to Indigo RC2 earlier today. The build broke immediately after my change, but looking at the console it seems not to be related to mat – one of the other participating update sites was not available. I’ll be looking at the aggregator build hoping to see a good build again. I uploaded also the RCPs for the different platforms. You can try out the results, links are available on the snapshotBuilds page: http://www.eclipse.org/mat/snapshotBuilds.php. I haven’t got yet any feedback from the tools PMC about the release documentation, but once this is clarified I think we are ready for the 1.1 release. Fixes for any non-critical problems (where MAT doesn’t work at all) will be postponed for the next releases. From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum I submitted the change which fixes the update problem. Andrew, if you want to try out just trigger a second (after the change) build in Hudson, and try updating the RCPs from the first using the update site from the second. I will make tomorrow the contribution to Indigo RC2 and will upload new RCPs. From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum Adding a mat.p2.inf file (next to the mat.product file) which specifies version ranges for the included features solves the problem. I could build twice and update the RCP feature of the older build with the newer feature. I will play some more with it and will publish another set of build results next week. Well I’ll also need to make the contribution to Indigo again to keep the versions of the bundles in sync. So far I tried specifying range [1.1.0, 2.0.0). Does this seem reasonable, or shall I try to leave the end open (not sure yet if I can do it…)? With this change the behavior is still that before the update the RCP feature is under the product, and after the update it is next to it. But I think this is something we can accept at the moment. From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum I think this describes the problem: http://aniefer.blogspot.com/2009/07/composing-and-updating-custom-eclipse.html I got some help from colleagues working on Tycho, let’s see if I can get the problem fixed… From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Tsvetkov, Krum Andrew, thanks for the hint! I built again and indeed I am not able to update the rcp with a similar error. I’ll look into it. BTW I tested upgrading a MAT 1.0.1 and this works fine… Krum From: mat-dev-bounces@xxxxxxxxxxx [mailto:mat-dev-bounces@xxxxxxxxxxx] On Behalf Of Andrew Johnson I tried installing the update site http://download.eclipse.org/mat/1.1/snapshots/20110518/update-site/ into a slightly older Windows 32 MAT: API 1.1.0.201105180316 Unless stated otherwise above: |