You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Carsten Ziegeler <cz...@apache.org> on 2008/02/18 18:01:48 UTC
Renaming jcr base module?
Hi,
I think that "jcr base" is a little bit to generic.
What about naming it "jackrabbit-base" as it is the base for the
jackrabbit-client and jackrabbit-server modules?
Carsten
--
Carsten Ziegeler
cziegeler@apache.org
Re: Renaming jcr base module?
Posted by Carsten Ziegeler <cz...@apache.org>.
Agreed
Carsten
Felix Meschberger wrote:
> Hi all,
>
> Looking at what is in the jcr/base module right now, I think we do not
> have to change the name.
>
> The bundle has two dependencies on Jackrabbit and its API: One is the
> node type loader which uses Jackrabbit API and the second is the
> RepositoryAccessor which uses the jackrabbit-jcr-rmi library to access a
> remote repository over RMI.
>
> Looking at the jcr/api reveals, that this bundle actually exports the
> Jackrabbit API, so it also has a dependency to Jackrabbit - and we never
> discussed renaming that.
>
> Of course, in Sling the jcr/base is only referred to by the
> jackrabbit-server and jackrabbit-client bundles. But other integrators
> of Sling may use the jcr/base module and extend it for their own JCR
> implementation used.
>
> Regards
> Felix
>
>
> Am Freitag, den 22.02.2008, 09:52 +0100 schrieb Bertrand Delacretaz:
>> On Fri, Feb 22, 2008 at 9:31 AM, Carsten Ziegeler <cz...@apache.org> wrote:
>>> ... jcr/commons is fine if it's not tied to jackrabbit :)
>>> Otherwise I would prefer a "jackrabbit" somehow in the name....
>> ok, so that'd be jackrabbit-base then.
>>
>> The RepositoryAccessor class uses some convenience classes from
>> Jackrabbit - not sure if those are really tied to Jackrabbit vs. other
>> JCR repositories, but it's still good to indicate that in the name.
>>
>> -Bertrand
>
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: Renaming jcr base module?
Posted by Felix Meschberger <fm...@gmail.com>.
Hi all,
Looking at what is in the jcr/base module right now, I think we do not
have to change the name.
The bundle has two dependencies on Jackrabbit and its API: One is the
node type loader which uses Jackrabbit API and the second is the
RepositoryAccessor which uses the jackrabbit-jcr-rmi library to access a
remote repository over RMI.
Looking at the jcr/api reveals, that this bundle actually exports the
Jackrabbit API, so it also has a dependency to Jackrabbit - and we never
discussed renaming that.
Of course, in Sling the jcr/base is only referred to by the
jackrabbit-server and jackrabbit-client bundles. But other integrators
of Sling may use the jcr/base module and extend it for their own JCR
implementation used.
Regards
Felix
Am Freitag, den 22.02.2008, 09:52 +0100 schrieb Bertrand Delacretaz:
> On Fri, Feb 22, 2008 at 9:31 AM, Carsten Ziegeler <cz...@apache.org> wrote:
> > ... jcr/commons is fine if it's not tied to jackrabbit :)
> > Otherwise I would prefer a "jackrabbit" somehow in the name....
>
> ok, so that'd be jackrabbit-base then.
>
> The RepositoryAccessor class uses some convenience classes from
> Jackrabbit - not sure if those are really tied to Jackrabbit vs. other
> JCR repositories, but it's still good to indicate that in the name.
>
> -Bertrand
Re: Renaming jcr base module?
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Fri, Feb 22, 2008 at 9:31 AM, Carsten Ziegeler <cz...@apache.org> wrote:
> ... jcr/commons is fine if it's not tied to jackrabbit :)
> Otherwise I would prefer a "jackrabbit" somehow in the name....
ok, so that'd be jackrabbit-base then.
The RepositoryAccessor class uses some convenience classes from
Jackrabbit - not sure if those are really tied to Jackrabbit vs. other
JCR repositories, but it's still good to indicate that in the name.
-Bertrand
Re: Renaming jcr base module?
Posted by Carsten Ziegeler <cz...@apache.org>.
Bertrand Delacretaz wrote:
> What do people think about the suggested renaming below?
>
> Right now jcr/base has only one class, so I assume we'll want to put
> more stuff there over time, so maybe jcr/commons is more appropriate.
>
jcr/commons is fine if it's not tied to jackrabbit :)
Otherwise I would prefer a "jackrabbit" somehow in the name.
Carsten
> -Bertrand
>
> On Tue, Feb 19, 2008 at 8:47 AM, Bertrand Delacretaz
> <bd...@apache.org> wrote:
>> Hi,
>>
>> On Feb 18, 2008 6:01 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>>
>> > ...I think that "jcr base" is a little bit to generic.
>>
>>> What about naming it "jackrabbit-base" as it is the base for the
>> > jackrabbit-client and jackrabbit-server modules?...
>>
>> Agreed, or jackrabbit-commons maybe?
>>
>> -Bertrand
>>
>
>
>
--
Carsten Ziegeler
cziegeler@apache.org
Re: Renaming jcr base module?
Posted by Bertrand Delacretaz <bd...@apache.org>.
What do people think about the suggested renaming below?
Right now jcr/base has only one class, so I assume we'll want to put
more stuff there over time, so maybe jcr/commons is more appropriate.
-Bertrand
On Tue, Feb 19, 2008 at 8:47 AM, Bertrand Delacretaz
<bd...@apache.org> wrote:
> Hi,
>
> On Feb 18, 2008 6:01 PM, Carsten Ziegeler <cz...@apache.org> wrote:
>
> > ...I think that "jcr base" is a little bit to generic.
>
> > What about naming it "jackrabbit-base" as it is the base for the
> > jackrabbit-client and jackrabbit-server modules?...
>
> Agreed, or jackrabbit-commons maybe?
>
> -Bertrand
>
--
Bertrand Delacretaz
http://www.codeconsult.ch
Re: Renaming jcr base module?
Posted by Bertrand Delacretaz <bd...@apache.org>.
Hi,
On Feb 18, 2008 6:01 PM, Carsten Ziegeler <cz...@apache.org> wrote:
> ...I think that "jcr base" is a little bit to generic.
> What about naming it "jackrabbit-base" as it is the base for the
> jackrabbit-client and jackrabbit-server modules?...
Agreed, or jackrabbit-commons maybe?
-Bertrand