Naming Conventions

Naming conventions for ModelAnt tasks:

Java package names

  1. The package name of any Java class of core component should be formed as:
    net.mdatools.<product>.<component>

    followed by

    • task if the class is an Ant Task
    • condition if the class is an Ant Condition
    • type if the class is a public Ant Types
  2. The package name of any Java class of meta-model specific component should be:
    net.mdatools.<product>.<meta-model>.<component>

    followed by:

    • task if the class is an Ant Task
    • condition if the class is an Ant Condition
    • type if the class is a public Ant Types
  3. The package name of model elements, of a defined by OMG meta-model should be
    org.omg.<meta-model>

    followed by model-specific package names, for example: org.omg.uml13.foundation.core.ModelElement

  4. The package name of model element wrapper, of a defined by OMG meta-model should be
    org.omg.<meta-model>.<component>

    followed by model-specific package names, for example: org.omg.uml13.wrap.foundation.core.WrapModelElement

  5. Any component-specific public constants should be held in Convention class in the component’s root package

AntLib file names

  1. The AntLib definitions file of a core component should be named:
    net/mdatools/<product>/<component>/antlib.xml

    in src/xml directory

  2. The AntLib definitions file of a meta-model specific component should be named:
    net/mdatools/<product>/<meta-model>/<component>/antlib.xml

    in src/xml directory

Leave a Reply

Your email address will not be published.

Time limit is exhausted. Please reload CAPTCHA.