FYI, I physically removed the xerces jars from the repo and it didn't
seem to cause any problems for the minimal assembly (deploying and
running a simple web app continued to work).
On a less positive note ... it looks like some things have been added to
push the size back up slightly ... to 17 meg now. I'm looking into what
has caused the increase along with trying to remove other items
mentioned as possibilities.
Several folks have voiced the idea that we may need to provide some
additional logic to either explicitly remove or include items in the
assembly image beyond that which is specified in the module and config
dependencies. However, I'm not sure if I understood the proposals.
It seems to me that something like this would require some duplicate
definitions ... such as:
1) Provide some per-assembly mechanism to define what is to be included
in the repo in addition to the module/config declarations. A dependency
would have to be both in some set of master dependencies and the
assembly declaration to be included in the image. An assembly would not
pull in additional dependencies without an assembly specific change.
2) The inverse per-assembly definition where items that should
specifically be excluded would be specified. This would help to
eliminate unnecessary items in an assembly but the definition of new
dependencies would affect the size of the image with each build by only
changing module/config dependencies (as is the case today).
Are these the options that were being proposed or did I totally miss the
intent of the comments?
Thanks,
Joe
Jeff Genender wrote:
David Jencks wrote:
Doesn't it need them in the classpath or in the endorsed directory
rather than specifically in the repo? right now we have 2 copies of
these and probably everything in lib. I at least am proprosing removing
only the copy in the repo.
IIRC, they must be in the endorsed. I don't recall if they need to be
in the classpath too...but that is a simple test.
thanks
david jencks
--
Joe Bohn
joe.bohn at earthlink.net
"He is no fool who gives what he cannot keep, to gain what he cannot
lose." -- Jim Elliot
