Yes we break ours projects into small one. Actually, we follow a multi
layer architecture so for 1 EAR we can have up to 10 modules.
It is difficult to break this application but I understood your point of
view...
The issue is that we often need to test our application that means
create the full EAR (a full multi module build) and deploy it to the
application server.
And unfortunately all the tests can not be done out of the container...
So how do you mange this long lifecycle ?
Thanks
Yann.
Graham Leggett a écrit :
Yann wrote:
In our company lot of people complains that our maven 2 builds are too
long.
We use multi modules and most of the time we only need to build 1 or 2
modules not all of them.
The ideal longer term solution is to break the project up into smaller
sections, either individual artifacts with their own life cycle, or
small multi module builds.
Try and separate out code that tends to change often, and code that does
not, and then put the code that doesn't change often into its own
release cycle.
You will also find you will have less problems this way, because each
release is a release of less code, and therefore there is less
opportunity for stuff to go wrong.
Regards,
Graham
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
