I've inherited a maven 1.0.2 build process we use in both development
and production of three different products. One of the majot goals in
the maven.xml is to build an ear that contains a WAR and ten-twenty
EJBs so it can be deployed later to a weblogic server 8.1. The goal
takes about fifteen minutes on a unix box. The subgoal (correct
terminology?) that takes 80-90% of the time (about twelve minutes) is
<weblogic:appc target="${earDestDir}" skip="false" includebuild="true"
/>
This subgoal takes the same amount of time rather no files are changed
or all files are changed. I assume this happens because there is an
attribute for weblogic:appc whose default is "build all even if nothing
is changed".
The developers (including me when I wear my developer hat) whine that
this takes way too long when all you're trying to do is verify a one
line change in a JSP. We would like this (possibly mythical) attribute
set (at least for development) to "build only what's necessary". I
can't guess what that attribute might be. Where do I go for advice?
Thanks, John Hines
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
