Yes, that's why I suggest to only update the guide to emphasize on EnclosureContainer and to have a big red warning before the section for <wicket:enclosure> saying "We do not accept bug reports for <wicket:enclosure> so do not use it" or something like that :-)
On Wed, Jan 23, 2019 at 2:54 PM Maxim Solodovnik <solomax...@gmail.com> wrote: > This is a lot ... > I face issues with enclosures so avoid using it in our project, so now > there are only 12. > > On Wed, 23 Jan 2019 at 17:54, Martijn Dashorst <martijn.dasho...@gmail.com > > > wrote: > > > On Wed, Jan 23, 2019 at 11:52 AM Martijn Dashorst > > <martijn.dasho...@gmail.com> wrote: > > > > > > On Wed, Jan 23, 2019 at 4:48 AM Maxim Solodovnik <solomax...@gmail.com > > > > wrote: > > > > > > > > +1 to make it deprecated and correct the documentation > > > > I'm also OK with removing it in 9.0.0, I believe there is enough time > > to > > > > fix 9.0.0 applications :) > > > > > > I'd rather not remove it in 9 (nor 10+). The solution to fix this in > > > applications is non-trivial, and removing the feature will break apps > > > considerably and silently. > > > > 635 occurrences of <wicket:enclosure in two of our major projects (143 > and > > 492) > > > > Martijn > > > > > -- > WBR > Maxim aka solomax >
