My vote is to set up deprecation of plugin now, and remove it completely for 3.0. Our tooling should be able to handle this stuff by then..
On 4/16/13 8:23 PM, "Joe Bowser" <bows...@gmail.com> wrote: >Only when we decide to drop plugin. >On Apr 16, 2013 8:14 PM, "Filip Maj" <f...@adobe.com> wrote: > >> https://issues.apache.org/jira/browse/CB-1109 >> >> >> We need to add a deprecation notice to change this, is that right? >> >>
