Mailing-List: contact dev-help@jackrabbit.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@jackrabbit.apache.org
Received-SPF: pass (athena.apache.org: domain of tmueller@day.com designates
 207.126.148.87 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4AE02074.4010001@gmail.com>
References: <91f3b2650910210719nfaa7681u6197d856d55e31c5@mail.gmail.com>
	 <4ADF3B4F.30004@gmail.com>
	 <91f3b2650910212347s52c41113gda9ffde12d627b39@mail.gmail.com>
	 <4AE02074.4010001@gmail.com>
Date: Mon, 26 Oct 2009 10:01:12 +0100
Message-ID: <91f3b2650910260201i39ab2549i6269e2cee2b90cc9@mail.gmail.com>
Subject: Re: Merging components
From: =?ISO-8859-1?Q?Thomas_M=FCller?= <thomas.mueller@day.com>
To: dev@jackrabbit.apache.org
Content-Type: text/plain; charset=ISO-8859-1

Hi,

> There have been reasons why the components were split in the first place

We should document the reasons. In what case do you use each of the
jackrabbit jar file alone? Why is this an important use case, and why
would it hurt if the other functionality is also included?

> ... So don't go overboard and say "always use it like this"

I wrote "_almost_ always used as one component".

> The total number of jars doesn't concern with me

Good to know, but please remember most people don't use OSGi.

> The only concern is the number of jars started with jackrabbit-*. I would dream to get a default repository just with jackrabbit-core.

Me too :-)

Regards,
Thomas