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
RepositoryAcce
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 libra
On Fri, Feb 22, 2008 at 9:31 AM, Carsten Ziegeler <[EMAIL PROTECTED]> 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 cla
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
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
<[EMAIL PROTECTED]> wrote:
> Hi,
>
>
Hi,
On Feb 18, 2008 6:01 PM, Carsten Ziegeler <[EMAIL PROTECTED]> 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?
-Bertra
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
[EMAIL PROTECTED]
