Community
Participate
Working Groups
Created attachment 166646 [details] ZIP of Modeling Discovery UI contributions Attached has a modeling.xmi with extra OCL Tools (Examples) and QVTd contributions. ocl.png qvtd.png screen snapshots to follow releng to ensure content in staging is presumably our problem.
Alex: this contribution makes the org.eclipse.ocl.examples feature loadable in a much more friendly and uniform fashion and like all the other contributors (except Xtext) expects the contributions to be available in http://download.eclipse.org/releases/staging/. Currently we only put the core OCL plugins there. We need to put the examples plugins and feature there too. Any idea how we do that/why we don't do that?
You should update your Helios build contribution (xx-ocl.build) to add your example feature. Have a look on the others .build files as direction. The modeling.xmi file has been updated, your components are going to be switched to visible once you provide me the missing screenshots.
Created attachment 170302 [details] OCL Screenshot Missing OCL screenshot.
Created attachment 170307 [details] QVTr screenshot Missing screenshot for QVTd. I hope you have everything Amalgam needs. I'll follow up on the Helios contribution tip.
(In reply to comment #2) > You should update your Helios build contribution (xx-ocl.build) to add your > example feature. Have a look on the others .build files as direction. Alex: /org.eclipse.helios.build/mdt-ocl.build should reference the ...master rather than the ...all.sdk feature to incorporate Examples in the copying/aggregating. Most projects seem to just use their composite feature, although we could specify examples separately emulating emf-cdo's multiple features. [I don't think we need the signature; all other projects get away with just version and qualifier.] Xtext is already there so we should not be adding any new dependencies. Are we (you) brave enough to do this? Now, just after RC2 and well before RC3, seems like a good time.
(In reply to comment #5) > (In reply to comment #2) > > You should update your Helios build contribution (xx-ocl.build) to add your > > example feature. Have a look on the others .build files as direction. > > Alex: /org.eclipse.helios.build/mdt-ocl.build should reference the ...master > rather than the ...all.sdk feature to incorporate Examples in the > copying/aggregating. Most projects seem to just use their composite feature, > although we could specify examples separately emulating emf-cdo's multiple > features. [I don't think we need the signature; all other projects get away > with just version and qualifier.] > > Xtext is already there so we should not be adding any new dependencies. Are we > (you) brave enough to do this? Now, just after RC2 and well before RC3, seems > like a good time. I think we need Kenn's +1. Moreover, I won't be able to check whether the changes are correct since helios.runBuckyBuild job has been disabled for 11 days by now - I suppose this is done on purpose. BTW, does anyone know why?
(In reply to comment #6) > I think we need Kenn's +1. Moreover, I won't be able to check whether the > changes are correct since helios.runBuckyBuild job has been disabled for 11 > days by now - I suppose this is done on purpose. BTW, does anyone know why? I'm not sure it's a good idea to replace the SDK at this point. Probably better to add an additional contribution for the examples, so that folks aren't forced to install something that has the examples if they don't want them...
(In reply to comment #7) > (In reply to comment #6) > > I think we need Kenn's +1. Moreover, I won't be able to check whether the > > changes are correct since helios.runBuckyBuild job has been disabled for 11 > > days by now - I suppose this is done on purpose. BTW, does anyone know why? > > I'm not sure it's a good idea to replace the SDK at this point. Probably better > to add an additional contribution for the examples, so that folks aren't forced > to install something that has the examples if they don't want them... +1 to adding examples as another new feature. Ed, do you agree?
Created attachment 170523 [details] OCL Examples feature added to mdt-ocl.build
Kenn, Ed, I need formal "+"s from you to commit the patch. Meanwhile, the bucky build job is still disabled. At the risk of being called a blockhead, I will ask it in the cross-projects list=))
(In reply to comment #10) > Kenn, Ed, > > I need formal "+"s from you to commit the patch. > > Meanwhile, the bucky build job is still disabled. At the risk of being called a > blockhead, I will ask it in the cross-projects list=)) Looks good to me.
+1 (although I think the signature following the qualifier is unnecessary).
(In reply to comment #12) > +1 (although I think the signature following the qualifier is unnecessary). I agree. Signatures removed. Committed.
(In reply to comment #13) > I agree. Signatures removed. Committed. Looking at Install New Software for releases/helios suggests that this extra signature may be a 'Borland' thing. You might like to alert your former colleagues.
(In reply to comment #2) > You should update your Helios build contribution (xx-ocl.build) to add your > example feature. Have a look on the others .build files as direction. > > The modeling.xmi file has been updated, your components are going to be > switched to visible once you provide me the missing screenshots. In RC3 EPP, we've successfully got the OCL examples to releases/staging without accidentally installing them always. All the screenshots are available. Could you please make MDT/OCL Examples visible, so that I can get a screenshot into a totorial. [M2M/QVTd requires me to crack promotion and ... much joy.]
I'm glad you managed to find your way through the complex maze of build and promotion. The OCL contribution have been activated. I tried to install it with RC3 and the install finished correctly.
Thanks. Promoting QVTd is still a treat in store - aggravated by not even knowing what the project name should be; I'm trying to migrate qvt-relations to qvtd.
