In the case of hbase-trx, the build runs multiple passes over the code in order 
to build multiple versions of the jar file for compatibility with multiple 
distros of HBase.

Unfortunately, the build works by creating and removing multiple versions of 
intermediate objects, which of course causes them to rebuild every single time.

The way it SHOULD work is to build each version of source/objects in 
version-specific directories and not delete them, so that rebuilds do not do 
the same work over again.

--Steve

> -----Original Message-----
> From: Dave Birdsall [mailto:[email protected]]
> Sent: Thursday, June 15, 2017 11:33 AM
> To: [email protected]
> Subject: make all suboptimal?
> 
> Hi,
> 
> Dumb question time.
> 
> Scenario:
> 
> I have a Trafodion development instance with a clean build. I make a one-line
> change to a C++ file and save it. Then I do a "make all". I notice that the
> "make all" seems to be rebuilding all the Java files - watching in "top" I see
> lots of heavy java processes going.
> 
> Question:
> 
> Why are the Java files rebuilt when they have not changed?
> 
> Dave

Reply via email to