The annotations used in the example can occur everywhere, not just at the type level. Perhaps that support is not needed for the first cut though.
On Tue, Sep 1, 2015 at 11:05 PM, Timothy Farkas <[email protected]> wrote: > Hey all, > > The japicmp plugin being used for Apex can be augmented to ignore classes > having a particular annotation. An additional field can be added to the > Maven configuration of the plugin such as the following: > > <excludeClassesAnnotatedWith> > > > > <annotation>org.apache.hadoop.classification.InterfaceStability.Evolving</annotation> > > > > <annotation>org.apache.hadoop.classification.InterfaceStability.Unstable</annotation> > </excludeClassesAnnotatedWith> > > If this change isn't incorporated into the main japicmp project, we may > have to consider forking and hosting the plugin. Please provide your > feedback/thoughts. > > In the meantime I'll pick up this ticket. Thanks, > Tim > > On Tue, Sep 1, 2015 at 9:20 PM, Chandni Singh <[email protected]> > wrote: > > > Logged a jira to address this. > > https://malhar.atlassian.net/browse/APEX-82 > > > > -Chandni > > > > On Tue, Sep 1, 2015 at 10:03 PM, Chandni Singh <[email protected]> > > wrote: > > > > > Hi, > > > > > > There are certain classes which can be annotated as Evolving or > Unstable. > > > Evolving: compatibility can be broken at minor release. > > > Unstable: no guarantee is provided as to reliability or stability > across > > > any level of release granularity. > > > > > > We need to ignore these classes from semantic versioning check. > > > > > > Regards, > > > Chandni > > > > > >
