apex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pramod Immaneni <pra...@datatorrent.com>
Subject Re: japicmp not configured to ignore @Evolving, @Unstable classes
Date Wed, 02 Sep 2015 15:19:51 GMT
+1

Consider using less verbose tag name.

On Tue, Sep 1, 2015 at 11:05 PM, Timothy Farkas <tim@datatorrent.com> 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 <chandni@datatorrent.com>
> 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 <chandni@datatorrent.com>
> > 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
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message