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
