What about 2 jars. The core, and everything else.
On 10/25/06, Julien Vermillard <[EMAIL PROTECTED]> wrote:
Le mercredi 25 octobre 2006 à 10:06 +0530, Vinod Panicker a écrit :
> On 10/25/06, Trustin Lee <[EMAIL PROTECTED]> wrote:
> > Hi community,
> >
> > We've been splitting MINA into multiple subprojects using Maven. We have
> > produced as many JARs as the number of subprojects. It was mainly due to
> > Java 1.4 compatibility to make sure the build doesn't fail even if a user
> > runs the build in Java 1.4. Now, situation has changed; we all agreed to
> > move to Java 5 and use Java 5 language constructs and APIs actively. Each
> > individual JARs are small enough to merge into one big JAR, and managing
> > MINA as one IDE project would be much easier to browse and develop with.
> >
> > WDYT? Is this a good idea?
>
> What about dependencies of the current subprojects? If I integrate
> MINA into my maven project, then all the dependencies will be
> automatically pulled into my assembly. If I want to exclude them,
> I'll have to manually include them in the pom and make the scope as
> 'compile'.
>
> We also don't know what future addons will be made to MINA, and
> whether they will fit well into a uber jar concept.
>
> That said, I think the convenience offered by moving to a single jar
> is quite a bit at the moment.
>
> Regards,
> Vinod.
Hi,
I'm not very fan of the idea, I like to have a mina-core.jar quickly
compiled, small and without a lot of dependencies because I'm very
limited in disk space and memory.
Julien
