[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [amp-dev] IAgentChild
|
I looked a little closer at this, and it seems that the changes did not get into the Indigo build...I was actually going against a slightly newer version. Weird. :)
On Jun 21, 2011, at 5:53 PM, Miles Parker wrote:
>
> Hi guys,
>
> The good news is that it looks like some of the important SD stuff got back into the final build, though technically we shouldn't have been making any changes. :) The bad news is that we ended up with a regression. See below.
>
> I'm a little worried that some stuff might have gotten written over in the process but I haven't looked carefully through everything. I'm honestly completely confused about when changes happened and what got into the build. :) I'm not sure what we decided to do with the whole IAgentChild thing. I guess perhaps get things working and then revisit. On balance, it is probably better to have the SD stuff working than to worry about having the "perfect" codegen for Escape. That's sort of the point of codegen. The problem though with the below is that it breaks the Ascape models since the definitely can't reference outside classes. Can we put the change back in so that this only affects the Escape generation? This won't work for Indigo but we can have a fix in the update site. Do you know when you put that back in and then when it was merged back and pushed to the main repos? I'm not trusting what git is telling me anymore.
>
> More generally, now that we're though the Indigo crunch, let's get back to the issue of how we can get the functionality below using the existing Ascape API as much as possible. Let's follow up on the relevant bug(s).
>
> http://git.eclipse.org/c/amp/org.eclipse.amp.git/commit/org.eclipse.amp.amf/plugins/org.eclipse.amp.amf.gen.escape/src/metaabm/escape/tmpl/EscapeAspect.xpt?id=a50c6901bc1abb1f1b5276b76af4af56ba0e527b
>
> Unfortunatly,
