Complete removal of the plugin was my solution to the problem of the jar file's dependencies. If it's not used or maintained, then it should be removed, in my opinion. Disabling it in the build is a good first step.
*Jeff Hair* Technical Lead and Software Developer Tel: (+354) 415 0200 j...@greenqloud.com www.greenqloud.com On Wed, Mar 15, 2017 at 8:18 AM, Rohit Yadav <rohit.ya...@shapeblue.com> wrote: > +1 as others have noted > > > Disable the plugin from the default build for next few releases and > eventually deprecate/remove the plugin from the codebase. The roadmap can > look something like: > > - Announce on the MLs that we're planning to do this, send a PR and get it > accepted > > - During the release process RM should make this information available to > everyone (including voting thread, would be nice to have a shortlog of > major changes in the voting email?) > > - In the release notes and release announcement, note that midonet is no > longer included in the default build and is planned to be deprecated > > - By end of the year, if we've no communication received deprecate and > remove the plugin with an announcement > > > I think this should be done with Midonet and any other plugins that are > causing issues and are no longer maintained by anyway. > > > Regards. > > ________________________________ > From: Sergey Levitskiy <sergey.levits...@autodesk.com> > Sent: 15 March 2017 07:00:51 > To: dev@cloudstack.apache.org > Subject: Re: [DISCUSS] Retirement of midonet plugin > > I am for: > (i) disable the build for the plugin for the next 2 major release > followed by > (ii) remove everything in ACS 4.12 if no one express regrets by then > > > > > rohit.ya...@shapeblue.com > www.shapeblue.com > 53 Chandos Place, Covent Garden, London WC2N 4HSUK > @shapeblue > > > >
