Issue with reference of Xtext composite update site in feature.xml

[pefribeiro]

Dear colleagues @UoY-RoboStar/plugin-developers ,

Recently, RoboTool fails to install most plug-ins due to an issue with update sites in Eclipse and the absence of GPG keys. This is similar to an issue we've previously identified, and for which the solution was to remove two update sites, namely Latest Eclipse IDE Packages Release and Latest Eclipse Simultaneous Release. Upon adding the RoboTool update site, Eclipse adds an update site with location https://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/, which seems to be causing a similar issue. Example below:

A current workaround is to remove the Xtext composite update site, that only appears after inputting the RoboTool update URL, thus adding extra steps for users to follow. Therefore, it would be good to fix this issue and this is my request to you.

I have narrowed the issue down to the category.xml of plug-ins that include an XML tag repository-reference with the above URL. I've also noticed that references in the same file and within target plug-ins also seem to refer to earlier versions of Eclipse. Therefore, it would be good if you could:

1. Revise the category.xml of fhe feature project of your plug-in and replace https://download.eclipse.org/modeling/tmf/xtext/updates/composite/releases/ by the URL used for the current version of Xtext https://download.eclipse.org/modeling/tmf/xtext/updates/releases/2.25.0/. Do check whether Xtext is really a required dependency of your specific plug-in, otherwise I think it could be removed?
2. Similarly, revise your target/repository project any update any tags that reference the Xtext URL.
3. Similarly, update any references to Eclipse update sites of https://download.eclipse.org/releases/2020-03 and replace them with https://download.eclipse.org/releases/2021-12, and or, as appropriate.
4. Test that you can compile your plug-in with Eclipse/Maven.
5. Update this thread as to whether you've completed the above, and if not applicable also please state so. If you wish, you can reference this issue by URL in a pull-request or commit text, that way GitHub will track changes in this thread automatically.

I'll update the following checklist as each relevant repo/plug-in is updated:

• robocert-csp-gen
• robocert-tikz-gen
• robocert-metamodel
• robocert-textual
• robochart-metamodel
• robochart-textual
• robochart-graphical
• robochart-csp-gen
• robochart-comparison
• robochart-prism-gen
• robochart-importer
• robochart-exporter
• robochart-2sim-tools
• robochart-expr-fdr-gen
• robosim-metamodel
• robosim-csp-gen
• robosim-textual
• robosim-graphical
• robosim-generator-template
• physmod-metamodel
• physmod-textual
• physmod-sdf-gen
• physmod-cpc-gen
• physmod-sdfpp-gen

[MattWindsor91]

Neither robocert-csp-gen nor robocert-tikz-gen are currently maintained (and I don't think they're exposed to the wider public). Would archiving them be enough to resolve the issue for now?

(Current robocert tool progress is in the form of robocert-hs until a robotool-friendly v0.2 compliant robocert tool can be made. The tikz generator was always experimental and is now very far behind.)

The last stable form of RoboCert's CSP generator was in robocert-textual, which I imagine does need to be fixed.

[pefribeiro]

Neither robocert-csp-gen nor robocert-tikz-gen are currently maintained (and I don't think they're exposed to the wider public). Would archiving them be enough to resolve the issue for now?

Thanks @MattWindsor91. I've updated the list.

The last stable form of RoboCert's CSP generator was in robocert-textual, which I imagine does need to be fixed.

Could you please look into the public plug-ins, robocert-metamodel and robocert-textual, and report if they need fixing? (As an aside, the feature "RoboCert Metamodel Developer Resources" is still miscategorized.)

[pefribeiro]

For robosim-graphical @madielfilho has made changes in https://github.com/UoY-RoboStar/robosim-graphical/tree/xtext_update_site.