Hi Somashekhar, Can you please open a bug and update with the details of why are we moving from javax.annotation to org.eclipse?
On Fri, Apr 26, 2019 at 3:29 AM SOMASHEKHAR MANOHARA JAVALAGI < [email protected]> wrote: > Hi Anil/Arun, > > I have raised a patch for changing of javax.annotation.Nonnnull > annotations from JSR-305 to org.eclipse.jdt.annotation library. Can you > please review and merge the same. > https://git.opendaylight.org/gerrit/#/c/81722/ > > Regards, > Somashekhar > > -----Original Message----- > From: [email protected] < > [email protected]> On Behalf Of Robert Varga > Sent: Wednesday, April 17, 2019 1:52 PM > To: Faseela K <[email protected]>; Róbert Varga > <[email protected]>; odlparent-dev < > [email protected]>; [email protected] > Subject: Re: [Odlparent-dev] sodium-mri : javadocs error : > javax.annotation.NonNull Error > > On 12/04/2019 09:14, Faseela K wrote: > > Robert, > > > > > > > > We are hitting the below error in genius while running javadocs on > > sodium-mri patch. > > > > There is no reference left for javax.annotation.Nonnull anywhere in > > genius, but still hitting this issue. > > I think this is an inherited annotation, i.e. it is specified in an > upstream API which genius implements -- and hence javadoc tries to access > it as part of documenting the types involved. > > I have staged a number of javax.annotation.Nonnnull removal patches > completely eliminating them from infrautils/serviceutils -- those should > help, but I think a similar effort needs to go into openflowplugin as well. > > Regards > Robert > > -- Thanks Anil
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
