I've got a project structured like this:
mylib/pom.xml /* parent and multi-module build; packaging: pom */
|
+-- mylib_core/pom.xml \
| | java projects which package as jar.
+-- mylib_util/pom.xml |
... |
+-- mylib_ext/pom.xml /
The standard maven build executed at mylib will produce
mylib_core-1.0.0.jar,
mylib_util-1.0.0.jar, mylib_ext-1.0.0.jar etc. Thanks to reactor the
dependencies between the parts are consulted and the parts are built
in the right order. Very nice.
"mylib" is also part of something I deliver to a client. They don't
use maven. I always deliver something like mylib-1.0.0.jar to them,
which combines the contents of all the submodules of mylib. From my
client's point of view how I choose to divide things into sub-modules
is an implementation decision of which he should not need to be aware.
Currently, I do this by hand. This is a pain. I'd like maven to
automate this. Is there a canonical way of doing this? I was quite
surprised not to find a standard assembly type for this scenario.
(There is one that will combine things into one jar, but it sucks in
all dependencies, transitvely -- which is not what I want.)
Is there a simple way to accomplish this, or should I just accept that
I'll once again have to beat my fingers bloody on the angle bracket
keys?
// Ben
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
