2012/1/10 Glenn Silverman gsilver...@dispensingsolutionsinc.com
Why not use the
maven-release-plugin to eliminate the manual process, you might wonder?
Great, then I have to modify each POMs scm element whenever I do a
SNAPSHOT-to-RELEASE, and, unless I use module inheritance in my POMs at
You might want to take a look at the versions plugin
(http://mojo.codehaus.org/versions-maven-plugin/) to change the root
POM and make the child modules fall in line (update-child-modules
goal).
Best maven practice seems to be that you don't try to release part of
a hierarchy. If there are
We had the same situation.
One of the things that we did as the application got more mature was to
decide that not all modules need to be at the same version number.
This was just an abstraction of the idea that we had already accepted
that third party libraries had different version number and
I really appreciate all the feedback so far. I see the problem as one of
build promotion, where you have a multi-module application with a
non-flat physical structure in Subversion; i.e.; the modules are nested
two or three deep, with a hierarchy of parent POM files. The actual
assembly module is,
We have a complex JavaEE app with multiple wars, jars, ds.xml and config
files, etc. In fact, there are over 80 different artifacts that make up
our application. We use the maven-assembly-plugin to create a gzip file
and untar it into a JBOSS instance to deploy and run. It's not pretty
and it's a
