well I am gonna be honest I never thought about it, but I think that
if you are running maven with *clean* option it will clean everything
and hence will need to recompile and rebuild stuff again, but this is
only what I think not really 100% sure.

On Mon, Oct 18, 2010 at 8:31 PM, Dan Haywood <[email protected]> wrote:
>  I use m2eclipse, which does differential builds using Eclipse's compiler.
>  This works well enough for me.  If I do a mvn from the command line, I tend
> to switch off automatic builds, do the build from the command line, then
> when I go back to Eclipse, do a full refresh, then switch automatic builds
> back on again.
>
> Related... if you are building from the command line, then mvn install is
> gonna be faster than mvn clean install, obviously.  In this sense maven is
> "change" aware.
>
> HTH
> Dan
>
> On 18/10/2010 19:42, Kevin Meyer - KMZ wrote:
>>
>> Is there any plan to make maven "change" aware, like "make"?  I find
>> it a little surprising that each build starts from the beginning, even if
>> no sources have changed!
>>
>> Or am I missing something?
>>
>



-- 
Thanks
- Mohammad Nour
  Author of (WebSphere Application Server Community Edition 2.0 User Guide)
  http://www.redbooks.ibm.com/abstracts/sg247585.html
- LinkedIn: http://www.linkedin.com/in/mnour
- Blog: http://tadabborat.blogspot.com
----
"Life is like riding a bicycle. To keep your balance you must keep moving"
- Albert Einstein

"Writing clean code is what you must do in order to call yourself a
professional. There is no reasonable excuse for doing anything less
than your best."
- Clean Code: A Handbook of Agile Software Craftsmanship

"Stay hungry, stay foolish."
- Steve Jobs

Reply via email to