Hi Simo,
On Mon, Dec 17, 2012 at 5:38 PM, Simone Tripodi
simonetrip...@apache.org wrote:
...I think we were not speaking about the same commons :P What I meant
is the java module[1] on SVN...
That's *jackrabbit* commons, what I was thinking of is *JCR* commons -
as AFAIU your utility only has
Hi,
On Mon, Dec 17, 2012 at 3:14 PM, Bertrand Delacretaz
bdelacre...@apache.org wrote:
What I see is http://jackrabbit.apache.org/commons/ which only
mentions jcr-rmi, and
http://svn.apache.org/repos/asf/jackrabbit/commons/ which has much
more than that - maybe the former needs to be updated
Hi Simo,
On Sun, Dec 16, 2012 at 1:02 AM, Simone Tripodi
simonetrip...@apache.org wrote:
...if you like the approach I described on
OAK-529 (patch with testcase included) I think we can discuss on more
additions...
IIUC what you suggest is only dependent on JCR APIs, not on Oak, right?
If
On Sun, Dec 16, 2012 at 1:02 AM, Simone Tripodi
simonetrip...@apache.org wrote:
...if you like the approach I described on
OAK-529 (patch with testcase included)
Looks nice!
On 17.12.2012, at 11:36, Bertrand Delacretaz bdelacre...@apache.org wrote:
If yes, that might better belong to a JCR
Hi all!
If yes, that might better belong to a JCR commons (sub)project - those
sorts of ideas regularly pop up, creating a modular library of such
reusable utilities might be useful.
+1, definitely something for jcr commons.
yes the addition just works for pure JCR APIs, it doesn't require
On Mon, Dec 17, 2012 at 12:51 PM, Simone Tripodi
simonetrip...@apache.org wrote:
... I am providing a new patch to be applied to jcr-commons...
Hmm...I didn't realize there was a jcr-commons already ;-)
What I see is http://jackrabbit.apache.org/commons/ which only
mentions jcr-rmi, and
Salut Bertrand,
I think we were not speaking about the same commons :P What I meant
is the java module[1] on SVN.
Anyway, the website needs to be updated about the commons you pointed on SVN :P
All the best,
-Simo
[1] http://svn.apache.org/repos/asf/jackrabbit/trunk/jackrabbit-jcr-commons/
