Issue #1254: test: Add SequenceDefaults test
Issue #1247, #1254: test: Tuple
Issue #1254: ClassTransformer: Allow anything of Empty type (such as "empty") as a defaulted annotation class parameter
Issue #1254: tests: Improve test
AnnotationBuilder: Delete unused class
Correct a field and getter name
LiteralAnnotationTerm: Move accessors
Factor out obtaining the value of a literal (or in the case of a negated natural literal, a literal-like) from the making of its JCTree. Add ErroneousException so exceptional cases can be dealt with easily.
Issues #1247, #1254: When building the annotation model, lets properly model each of the possible parameter types.
Issues #1247, #1254: Support building the new annotation metamodel annotations
Issues #1247, #1254: Encapsulate how we create the annotations on the DPM within the literal subclasses
Issues #1247, #1254: Add @ParameterValue
Issues #1247, #1254: test: Update a .src because of the new @ObjectValue annotation.
Issues #1247, #1254: Support parameters and tuples/sequences containing parameters in the annotation model. Ignore them when outputting fields.
Issues #1247, #1254: Make the various *LiteralAnnotationTerms single-valued, override toString(), and implement makeDpmAnnotations(). Add kinda-crufty AbstractTransformer.makeAnnoAnnotation() so I can see the wood for the trees in the annotation tests.
Issues #1247, #1254: test: Update some .src now we're emitting these @*Value annotations on DPMs.
Issues #1247, #1254: AbstractTransformer: annotation classes/constructors can have parameters of any subtype of model.Declaration, not just model.Declaration exactly.
Issues #1247, #1254: ClassTransformer: When calling Util.parseMetamodelReferences, supply a type argument
Issues #1247, #1254: ExpressionTransformer: Factor out the logic about getting the Declaration from a MetaLiteral.
Issues #1247, #1254: Refactor how we build the model, to support SequenceEnumerations, and maybe Tuples, and also refactor how we build the annotations for the DPMs.