Community
Participate
Working Groups
The Eclipse OCL Update sites have names starting "Eclipse OCL", so they appear under E in an alphabetic project list. Suggest removing the "Eclipse" prefix. Worth checking what a Dresden OCL site looks like. If necessary, we could be "OCL (Eclipse)".
"MDT/OCL" changed to "Eclipse OCL". Honestly I prefer Eclipse OCL rather than OCL (Eclipse). The category name of the repository is also "Eclipse OCL blablabla". I understand your point, tough. On the other hand, if you type "OCL" both sites would appear (Eclipse OCL and OCL (Eclipse)", so I'm not sure if the change is really necessary. N.B: I think that the names for the our public repositories should be aligned with the name we decide for the own generated repository (See Bug 368566). Different options : a) "MDT/OCL" b) "Eclipse OCL" c) "OCL (Eclipse)" d) "Object Constraint Language (OCL)". You decide ;) Cheers, Adolfo.
This is very low priority. Change to enhancement. I'll do some more study of project lists and see what others do.
Created attachment 210465 [details] Example menu list Attached is an example of the update site jumble that I get on M5. I consider that EMF Compare, Ecore Tools, MWE and Xtext have good names. I think we could do better by dropping the Eclipse at the front. The Dresden OCL site at http://www.dresden-ocl.org/update/site.xml prefixes its name with Dresden OCL so there is no ambiguity if we just OCL because we are the Eclipse OCL project.
So, Changing the name of our build features as follows: Eclipse OCL Core Build Site -> OCL Core Build Site Eclipse OCL Tools Build Site -> OCL Tools Build Site Regards, Adolfo.
Verifying that the generated repositories from our last Core/Tools builds have the proper one. Commit 13f622ca6ff67d1a26d38d7bb43d2084b21349c7 pushed to master. Resolving as fixed.
CLOSED after a year in the RESOLVED state.
