eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0
0 stars 0 forks source link

BaseCS.genmodel out of sync #1586

Closed eclipse-ocl-bot closed 1 month ago

eclipse-ocl-bot commented 1 month ago

| --- | --- | | Bugzilla Link | 473030 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Jul 19, 2015 17:45 EDT | | Modified | Jul 26, 2015 09:10 EDT | | Reporter | Marcus Huewe |

Description

The BaseCS.genmodel is not in sync with the BaseCS.ecore. For example,\ it still has a genClass entry for a "LibraryCS" element, which was removed\ from the BaseCS.ecore in commit eabec16cfe6b4c2d6aa663e6842a278bae980103.\ So it would be nice, if you could "reload" the genmodel.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Jul 25, 2015 05:38

Can do, but it should not be necessary.

The GenModel editor and our auto-generation scripts perform a "reconcile" after loading since stale *.genmodel is the normal state of any project under development.

Can you identify what activity has caused you to raise this. I can imagine for instance that the Xtext indexer/builder might be confused.

eclipse-ocl-bot commented 1 month ago

By Ed Willink on Jul 26, 2015 09:10

(In reply to Ed Willink from comment #1)

The GenModel editor and our auto-generation scripts perform a "reconcile" after loading since stale *.genmodel is the normal state of any project under development.

The auto-generation scripts can auto-save the reconciled models and avoid this happening again.

5 models get updated by this auto-save, incurring only one actual 'change' for a previously overlooked missing @Override.

Manually reloading provoked genuine changes by detecting that OCLinEcoreCS and OCLstdlibCS do not actually depend on EssentialOCLCS. Although no tests fail, the change in usedPackages is perhaps undesirable for a maintenance release, so keep the redundancy.

commit 75937f8bc1b117f5163f46176a7730bbb8da6085 pushed to maintenance/R6_0 for SR1

commit b085aab0b34ec59c8066aa4b116fd60d8af92742 pushed to master for M1