Community
Participate
Working Groups
The CDO Integration feature can be expected to get more attention (and testing!) from the user community if it is discoverable in the Papyrus Additional Components discovery system. So, it should be added to the discovery repository as an "experimental" component (this being its initial release).
I'll work on this.
Created attachment 229690 [details] Patch adding CDO features to component discovery Attached a patch that adds the CDO integration features (run-time and doc) to the additional components discovery manifest. Note that * the icon is, of course, not actually in the patch * the M7 milestone P2 repository does not exist, yet, so I won't be able to push this until after M7
Hi, Camille, When you have a moment, I'd appreciate your review of the attached patch to ensure that I understood how the discovery manifest works and that it would be correct when published. (note, of course, that this cannot be published until after M7) Thanks!
Created attachment 229693 [details] What the discovery dialog looks like I've attached a patch showing what the discovery dialog looks like when I direct it to the papyrus-extra.xmi in my local Git clone. The other components indicate that they aren't available because the M2 repository that they point to for p2 URLs no longer exists. I can fix that while I'm updating this file, anyways.
Created attachment 229694 [details] Updated screenshot for 72 dpi Oops, I forgot that I'm on a "Retina" Mac display at 144 DPI graphics. I've attached a new screenshot that is scaled down to what Windows PC users would see.
Hi Christian, > When you have a moment, I'd appreciate your review of the attached patch to ensure that I understood how the discovery manifest works and that it would be correct when published. It's fine. I have a single comment, regarding the documentation (Related to Bug 405625). I think it's better to provide all the documentations in a single doc feature (Which already exists), than to include it with the extra-component. That's what I've done for the CSS component. It's an extra component, but the doc is part of the global Papyrus documentation feature, and it includes Installation steps. So, the cdo.doc.feature should be removed from the discovery site. Thank you
Thanks, Camille. Wouldn't it be confusing, though, for users to see documentation of a component that isn't installed? I would add a note that the CDO feature needs to be installed from via the discovery site, of course, but still ... Moreover, this would mean that the main build has to be configured in the ramp to find the doc plug-in in the extra-plugins area.
(In reply to comment #7) > > Moreover, this would mean that the main build has to be configured in the > ramp to find the doc plug-in in the extra-plugins area. Oops, iPhone corrected the Buckminster "RMap" as "ramp".
(In reply to comment #7) Hi, Camille, Sorry to nag, but do you have any comment on my concerns (below) ? Thanks! > Thanks, Camille. Wouldn't it be confusing, though, for users to see > documentation of a component that isn't installed? I would add a note that > the CDO feature needs to be installed from via the discovery site, of > course, but still ... > > Moreover, this would mean that the main build has to be configured in the > rmap to find the doc plug-in in the extra-plugins area.
Hi Christian, Sorry for the delay. I've asked the team, and it seems more interesting to provide the doc as part of the Papyrus main component (In the papyrus.doc feature). It gives more visibility to the component, and the user can have an overview of the component before actually installing it (So he can decide whether he needs it or not), as well as an installation guide. The CDO doc plug-in can be moved to plugins/doc to avoid build issues (The rmap will still need to be updated, but it's not a big deal)
Thanks, Camille. I can add a bit to the doc, then, explaining how to install the CDO integration feature. There is no plugins/doc folder: shall I create it, then? I suppose this is why you suggest that the rmap would still have to be updated, because if it doesn't exist, then obviously it isn't mapped, yet.
Hi, I've just added the doc folder to the SVN repo, and updated the rmap accordingly
r10948: The CDO doc plug-in is move from svn+ssh://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/extraplugins/cdo/org.eclipse.papyrus.cdo.ui.doc to svn+ssh://dev.eclipse.org/svnroot/modeling/org.eclipse.mdt.papyrus/trunk/plugins/doc/org.eclipse.papyrus.cdo.ui.doc and is now included in the org.eclipse.papyrus.doc.feature feature. The org.eclipse.papyrus.extra.cdo.doc feature is removed from the build.
commit e16a9d2817da158e5adce3046e51d653d9a12328 As the doc plug-in is no longer included in the discovery component because it is now in the main build, there is no impediment to publishing the CDO Integration component in the discovery site. I was only holding off until M7 because the documentation hadn't been published in any milestone update-site where discovery could find it. So, the discovery site is now updated to publish the M6 milestone of the CDO Integration feature.
