You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@abdera.apache.org by James M Snell <ja...@gmail.com> on 2008/02/14 22:08:17 UTC

One Jar To Rule Them All

Currently we ship lots of jars.  Despite being somewhat confusing, this 
can be a really good thing because it allows developers to pick and 
choose subsets of functions/features they wish to ship.  It does, 
however, make it more difficult when you really do want everything.

Therefore... I'm thinking about updating the build to produce a single 
all-inclusive jar in addition to the individual jars we currently have.

Any objections?

- James

RE: One Jar To Rule Them All

Posted by Remy Gendron <re...@arrova.ca>.
I recently entered a JIRA (https://issues.apache.org/jira/browse/ABDERA-115)
around this issue.

Remy

-----Original Message-----
From: James M Snell [mailto:jasnell@gmail.com] 
Sent: February 14, 2008 16:08
To: abdera-dev@incubator.apache.org
Subject: One Jar To Rule Them All

Currently we ship lots of jars.  Despite being somewhat confusing, this 
can be a really good thing because it allows developers to pick and 
choose subsets of functions/features they wish to ship.  It does, 
however, make it more difficult when you really do want everything.

Therefore... I'm thinking about updating the build to produce a single 
all-inclusive jar in addition to the individual jars we currently have.

Any objections?

- James

No virus found in this incoming message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.5/1278 - Release Date: 2008.02.14
10:28
 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.20.5/1278 - Release Date: 2008.02.14
10:28
 


Re: One Jar To Rule Them All

Posted by Adam Constabaris <ad...@clownsinmycoffee.net>.
On 14-Feb-08, at 5:16 PM, Dan Diephouse wrote:

>

> I think this is a good idea. I've been meaning to do this as part of  
> the Maven distribution I started on (locally).
>
> In the distribution - do we want to have both the uber jar and the  
> module jars?


The uber+modular strategy works well for Spring; it makes it easier on  
those deploying servers, while still supporting (as much as possible)  
a "slim" profile for (e.g.) mobile clients.

Which is a long-winded way of saying +1 =)

AC

Re: One Jar To Rule Them All

Posted by Dan Diephouse <da...@mulesource.com>.
James M Snell wrote:
> Currently we ship lots of jars.  Despite being somewhat confusing, 
> this can be a really good thing because it allows developers to pick 
> and choose subsets of functions/features they wish to ship.  It does, 
> however, make it more difficult when you really do want everything.
>
> Therefore... I'm thinking about updating the build to produce a single 
> all-inclusive jar in addition to the individual jars we currently have.
>
> Any objections?
>
> - James
I think this is a good idea. I've been meaning to do this as part of the 
Maven distribution I started on (locally).

In the distribution - do we want to have both the uber jar and the 
module jars?

- Dan

-- 
Dan Diephouse
MuleSource
http://mulesource.com | http://netzooid.com/blog