These standard AntX definition interfaces should be implemented by your components if they publicly support the function embodied by the parameter. Using a single set of interfaces gives a consistent script-facing interface to similar functionality— which is particularly valuable for condition implementations that are supported by the short hand format of the various AntX build-rule tasks. Because AntX cannot guarantee the order in which the condition's parameters will be declared (or processed) it must be able to horde the modifiers until it knows the actual rule being created; only then will it apply the modifiers using these standard parameter interfaces. The AntX conditions and rule tasks rely heavily on these definition interfaces for most of the common AntX condition modifiers.
The parameters package classes can only depend on the following JWare packages: The top-level apis package (idaremedia.apis) and the top-level helpers package (antx.helpers). This package is used by the antx package, it cannot depend on anything in that package. The only concrete classes included in this package are the custom Ant "enum" selectors that can constrain a parameter's value choice.