Inadequate API Tooling management

eclipse-ocl / org.eclipse.ocl

Eclipse Public License 2.0

0 stars 0 forks source link

Inadequate API Tooling management #1444

Closed eclipse-ocl-bot closed 2 hours ago

eclipse-ocl-bot commented 2 hours ago

| --- | --- | | Bugzilla Link | 458732 | | Status | RESOLVED FIXED | | Importance | P3 normal | | Reported | Jan 29, 2015 07:39 EDT | | Modified | Jan 29, 2015 17:17 EDT | | Reporter | Adolfo Sanchez-Barbudo Herrera |

Description

I can spot a couple of anomalies with respect to API tooling management:

org.eclipse.ocl.examples.common and org.eclipse.ocl.examples.modelregistry contains error related to versions increments
ocl-buckminster.script is not adding the API baseline, which presumably could detect this API management deficiencies (I'm unsure why an the build doesn't complain about inexistent API baseline)
It seems there is not a consistent policy across API tooling usage. Should examples projects enable API tooling or not ?

eclipse-ocl-bot commented 2 hours ago

By Ed Willink on Jan 29, 2015 11:21

org.eclipse.ocl.examples.modelregistry is not in 6.0.0 we could fix the error for over-enthusiastic GIT users.

org.eclipse.ocl.examples.common has occasionally had an error in my workspace but it vanishes before I investigate. It is almost dead, not used by promoted plugins. But we should fix the error.

No baseline needs fixing, maybe I commented it out during some build fight and neglected to restire it.

My intended API policy is

API tooling for non-examples plugins at all time
API tooling for examples plugins in maintenance releases

I tried enabling API tooling for the pre-promoted examples plugins to maximize interim Luna compatibility, but it was totally unmanageable.

eclipse-ocl-bot commented 2 hours ago

By Ed Willink on Jan 29, 2015 16:34

org.eclipse.ocl.examples.common is only used by org.eclipse.ocl.examples.modelregistry.

The API problemaroses from the migration of the best bits to org.eclipse.ocl.pivot.

Choice 1:

They are dead, so just move to archive.

Choice 2:

Give them a major version change, so that they are useable from GIT.

The Buckminster

addbaseline -A "Eclipse OCL API Base Line"

is in ocl-fetch-buckminster.script, so I think the API violation is detected. It's just that the 'offending' plugins are not in the Buckminster workspace.

eclipse-ocl-bot commented 2 hours ago

By Ed Willink on Jan 29, 2015 17:17

(In reply to Ed Willink from comment #2)

Choice 2:

Give them a major version change, so that they are useable from GIT.

Does no harm. org.eclipse.ocl.examples.modelregistry depenedency on org.eclipse.ocl.examples.common also removed so that they can be independently moved to archive.