[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [emft-dev] [MWE] API break in 1.1
|
That's ok.. :) What I've tried to do for now is put in a dependency for 1.0.2 and 1.1, but obviously that's a rubber band solution and I haven't tested it with automated build yet. The trouble with upgrading the API right now is that there is actually a fair amount of low level stuff I've done to get things working with respect to markers, error logging, and so on, and I'm really afraid of monkeying around with it right before EclipseCon. (There is a new contribution that was just made that I'd really like to get in for that.) So...a compatibility layer would be really great. It would not have to be pretty at all, just recover the functionality, and spin it out to the nightly. OTOH, if looking at the code you can see an easy thing to try to recapture the functionality I'll give that a shot first and see if everything else works too: As you can see, what I'm doing there is capturing the issues as there didn't seem to be any more direct way to do that.
-Miles
On Mar 16, 2011, at 8:11 PM, Sven Efftinge wrote:
> Sorry Miles,
>
> I didn't think about API breakage when I applied the patch (stupid me).
> We don't want to increase the major version number.
>
> Is it possible for you to upgrade to the new API, or should we add a compatibility layer?
> I will be more careful next time, promised :-)
>
> Sven
>
> On Mar 16, 2011, at 2:33 PM, Miles Parker wrote:
>
>> Hi guys,
>>
>> In re: to my cross-project post, please see:
>>
>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=340242
>>
>> It's not entirely clear to me that the break occurred in 1.1.0 or if you have a plan to change version numbering to 2.0.0 for Indigo? I'm looking at http://www.eclipse.org/modeling/emft/downloads/?project=mwe and it lists 2.0.0 but the update coming from indigo is 1.1.0 with the breaking change.
>>
>> cheers,
>>
>> Miles
>>
>>
>> _______________________________________________
>> emft-dev mailing list
>> emft-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/emft-dev
>
> _______________________________________________
> emft-dev mailing list
> emft-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/emft-dev
