Eclipse Community Forums: EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Facet] non respect of the API freeze

Help

Home

Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » [EMF Facet] non respect of the API freeze

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

[EMF Facet] non respect of the API freeze [message #869856]

Fri, 04 May 2012 10:38

Gregoire Dupe
Messages: 71
Registered: September 2009
Location: France

Member

Hello,

Regarding the development plan, the development of EMF Facet 0.2 is really late. Main enhancements required by Papyrus have not been achieved before M6. We are not so far to finish. But, under the supervision of the PMC (http://markmail.org/message/lejrp6und7mhn35g#query:+page:1+mid:4joy7olr5jrqa7np+state:results), we had to commit modifications which didn't respect the M6 API freeze :

1) The plug-in 'org.eclipse.emf.facet.aggregate.ui' has been released (in 0.2 M6) but it was totally useless and it didn't contain any public API. It was really useful to remove it in the M7 release but another project may have a dependency to the plug-in 'org.eclipse.emf.facet.aggregate.ui'.

Cf. Bug 376574 - [Aggregate] Removing of the plug-in org.eclipse.emf.facet.aggregate.ui (https://bugs.eclipse.org/bugs/show_bug.cgi?id=376574)

2) The meta-model in 'aggregate-0.2.0.ecore' contained too many useless attributes and references. We chose to remove them rather than have to deal with them (for the users and the maintainers).

Cf. Bug 376575 - [Aggregate] aggregate-0.2.0.ecore cleanning (https://bugs.eclipse.org/bugs/show_bug.cgi?id=376575)

3) In the facet meta-model, the eReference Facet::extendedFacet didn't have the right multiplicity (should be -1 instead of 1).

Cf. Bug 376576 - [EFacet] Change the multiplicity of Facet::extendedFacet (https://bugs.eclipse.org/bugs/show_bug.cgi?id=376576)

4) The interface org.eclipse.emf.facet.efacet.metamodel.v0_2_0.efacet.query.QueryPackage was not marked with the tags '@noimplement' and '@noextend'. This was to avoid to add new eClasses without breaking the API. It would be really useful to add them before the M7 release.

Cf. Bug 376577 - [EFacet] '@noimplement' and '@noextend' in QueryPackage (https://bugs.eclipse.org/bugs/show_bug.cgi?id=376577)

I proposed to commit those modifications after M6, because I was expecting this will be less disturbing for the community than to get ugly features for a few years. Furthermore, EMF Facet is in the incubation state. I think we should benefit from this state to provide an as clean as possible product.

Regards,
Grégoire Dupé

Report message to a moderator

Previous Topic:	[TEXO] JPA Foreign Key
Next Topic:	[Texo] No Dao class is generated for abstract class

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Mon May 20 09:26:23 EDT 2013