Eclipse Community Forums: GMF (Graphical Modeling Framework) » GMF Codegen 2.9

Help

Home

Home » Modeling » GMF (Graphical Modeling Framework) » GMF Codegen 2.9 - API breakage?

Show: Today's Messages :: Show Polls :: Message Navigator

GMF Codegen 2.9 - API breakage? [message #888819]

Mon, 18 June 2012 17:05

Martin Fluegge

Messages: 141
Registered: July 2009

Senior Member

Hi,

we (CDO/Dawn) recently updated our baseline and found the one of our
bundle now show API errors which did not appear the last time. After
digging around we found out that our baseline now contains gmf.codegen
2.9 indead of version 2.2.
While we are re-expoting the tooling bundles we are also effected by the
changes. The problem is that although the versions only change in the
minor segment it seems that GMF tooling made a major version jump
because some classes have been deleted or removed from the API (see
traces below). Is this intentional or did this happen by mistake?

Thanks in advance.

Cheers,

Martin

Traces
--------------------------

Description Resource Path Location Type
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.GenTemplateInvocationItemProvider has
been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.GenVisualEffectItemProvider has
been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.OclChoiceParserItemProvider has
been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.PredefinedEnumParserItemProvider
has been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The major version should be incremented in version 2.0.0, since API
breakage occurred since version 2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 5
Version Numbering Problem
The re-exported type org.eclipse.gmf.codegen.gmfgen.OclChoiceParser has
been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type org.eclipse.gmf.codegen.gmfgen.GenVisualEffect has
been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.GenTemplateInvocationBase has been
removed from org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0
MANIFEST.MF /org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF
line 1 Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.GenTemplateInvocation has been removed
from org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0
MANIFEST.MF /org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF
line 1 Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.GenTemplateInvocationBaseItemProvider
has been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.GenFixedInputsTemplateInvocationItemProvider
has been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.provider.GenCustomGeneratorExtensionItemProvider
has been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type org.eclipse.gmf.codegen.gmfgen.PredefinedEnumParser
has been removed from
org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0 MANIFEST.MF
/org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF line 1
Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.GenFixedInputsTemplateInvocation has been
removed from org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0
MANIFEST.MF /org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF
line 1 Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.GenCustomTemplateInput has been removed
from org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0
MANIFEST.MF /org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF
line 1 Compatibility Problem
The re-exported type
org.eclipse.gmf.codegen.gmfgen.GenCustomGeneratorExtension has been
removed from org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit_2.0.0
MANIFEST.MF /org.eclipse.emf.cdo.dawn.codegen.dawngenmodel.edit/META-INF
line 1 Compatibility Problem

Report message to a moderator

Re: GMF Codegen 2.9 - API breakage? [message #889621 is a reply to message #888819]

Tue, 19 June 2012 12:17

Michael Golubev

Messages: 383
Registered: July 2009

Senior Member

Hello,

This classes indeed had been _added_ in 2.9 for Juno.
There were neither removed classes nor changes that may break binary backward compatibility.

To my understanding the problem is that added API classes don't have @since 2.9 javadoc.

Regards,
Michael

Report message to a moderator

Re: GMF Codegen 2.9 - API breakage? [message #889944 is a reply to message #889621]

Wed, 20 June 2012 10:48

Martin Fluegge

Messages: 141
Registered: July 2009

Senior Member

Hi Michael,

thanks for the quick response. If no classes have been removed, we can
ignore the warnings.

Cheers,

Martin

Am 19.06.2012 14:17, schrieb Michael Golubev:
> Hello,
> This classes indeed had been _added_ in 2.9 for Juno. There were neither
> removed classes nor changes that may break binary backward compatibility.
> To my understanding the problem is that added API classes don't have
> @since 2.9 javadoc.
> Regards, Michael

Report message to a moderator

Previous Topic:	How to arrange the property
Next Topic:	Customize property view

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon Jan 20 11:50:58 GMT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter