RFR: JDK-8196356: Changes to m4 files don't trigger autoconf execution at build time

Alan Bateman Alan.Bateman at oracle.com
Mon Feb 12 12:01:11 UTC 2018

On 12/02/2018 11:42, Magnus Ihse Bursie wrote:
> Why would hidden files be confusing? Or, rephrased, how is this any 
> more confusing than other hidden directories, such as .idea or .jib? I 
> modelled the behaviour on jib. In fact, I was considering using the 
> same directory (.jib), but since the name was so specialized, it felt 
> like misusing it. That's why I gave it a more general name. (In fact, 
> I believe, if .build had been present when jib was created, it would 
> have used that instead of creating the specialized .jib directory).
I'm aware of at least 10 people that ran into problems in the latter 
part of last week because they didn't know about the .build directory. I 
think most people are used to blowing away the build directory, the 
.build directory is new so we need to learn to blow away that too 
(irrespective of whether the build re-generated when it seems the time 
stamp is old). All I'm saying is that hidden directories have a tenancy 
to confuse. I can't comment on .jib as that is not in OpenJDK.


More information about the build-dev mailing list