30 Sep
2011
30 Sep
'11
11:10 a.m.
On Sep 30, 2011, at 9:06 AM, Thomas Mortagne wrote:
On Fri, Sep 23, 2011 at 1:25 PM, Vincent Massol
<vincent(a)massol.net> wrote:
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
On Sep 23, 2011, at 1:08 PM, Thomas Mortagne wrote:
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. 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.