Re: [gmf-dev] Generated NOT for class hierarchy

[Ed Merks <ed.merks@xxxxxxxxx>]

Igor,

I think it's probably better to use the forum not the developer mailing list.

There are two solutions.  One is to use something other than @generated NOT, e.g., @generated not, to block just the merging of the extends/implements part of the class/interface but still allow merging of the nested contents.  Another approach (better I think) is to use @extends/@implements (they do the same thing) in the user-doc section of the code.  E.g., like we do in EClassifierImpl as follows:


/**
 * <!-- begin-user-doc -->
 * An implementation of the model object '<em><b>EMeta Object</b></em>'.
 * @extends BasicExtendedMetaData.EClassifierExtendedMetaData.Holder
 * <!-- end-user-doc -->
 * ...............
 * @generated
 */
public abstract class EClassifierImpl extends ENamedElementImpl implements EClassifier, BasicExtendedMetaData.EClassifierExtendedMetaData.Holder
{

Then the JMerger will add those things automatically each time.

On 01/04/2013 12:16 PM, Igor Zapletnev wrote:

Hi,

I want to add additional interface for my edit part, for example. In this case I need to add @generated NOT annotation in the header of the file.

Probably I can add my custom interface without annotation in the header?

Somth like that

/**

 * @generated

 */

public class NameEditPart extends CompartmentEditPart implements

ITextAwareEditPart, /** @generated NOT */ MyInterface {

Thanks,

Igor

_______________________________________________
gmf-dev mailing list
gmf-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/gmf-dev