On 10/07/2011 09:22 AM, Thomas Mortagne wrote: > Just seen that we have a bunch of display related method based on > Query plugin for which we don't have any alternative to propose right > now. > > Basically it's supposed to allow to easily display a search form for > any field the same way you can display a edit form. > > Note that from what I understood from a conversation we had with > Denis it's not working very well. > > So what do we do after all ? > > 1) nothing > 2) still deprecate and move to legacy, is app within minutes supposed > to provide an alternative ? > 3) move to retired > > WDYT ? > > I'm now -1 for 3) since it's impossible to move method to retired. > > I would says lets still deprecate and move it to legacy even if we > don't provide right now an exact alternative, it's not like it was > making impossible to search something since we don't use this at all > in XE/XEM since a very long time AFAIK.
Indeed, those methods haven't been used in a while. Ludovic should know where (if) they're used. I also vote for 2. The displaySearch methods should be fixed later. > On Fri, Sep 30, 2011 at 11:10 AM, Vincent Massol<[email protected]> wrote: >> >> On Sep 30, 2011, at 9:06 AM, Thomas Mortagne wrote: >> >>> On Fri, Sep 23, 2011 at 1:25 PM, Vincent Massol<[email protected]> wrote: >>>> >>>> On Sep 23, 2011, at 1:08 PM, Thomas Mortagne wrote: >>>> >>>>> Hi dev, >>>>> >>>>> The new query manager component work pretty well and starts to be used >>>>> more and more so I think we should remove com.xpn.xwiki.plugin.query. >>>>> >>>>> So here is the proposals: >>>>> (1) move it to legacy >>>>> (2) move it to retired is it's own maven project so that it's easy to >>>>> build and produce a jar if someone wants to use it >>>>> >>>>> Note planning to do it in 3.2, that's for 3.3M1. >>>>> >>>>> WDYT ? >>>>> >>>>> +1 for (2): it's the last thing that trigger dependency on jackrabbit >>>>> so even if we get rid of jackrabbit in oldcore by moving it to >>>>> legacy-oldcore it would still be in XE >>>> >>>> I'd say (1) then (2) since it could be used by some external code. >>> >>> It's the same for any other things we retired. The question is more do >>> we still want to maintain it (legacy) or not (retired), in both case >>> anyone can still use it if he really wants either by using the 3.2 >>> version or building the retired one. >> >> Denis said he was still using it so I'd say yes to put it in legacy for now. >> Denis, how long should it stay there in your opinion? >> >> Thanks >> -Vincent -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
