How to check out the openjdk source code from the mercurial repositories

[Kelly O'Hair]

On Mar 15, 2011, at 2:05 AM, Steve Poole wrote:

>> 
>> A singular process that everyone uses?  Good Luck with that. I think that is called "herding cats". :^)
>> Sorry, I've been doing this too long, if there is a variation on doing development and one person finds
>> it productive for them, they will use it.
>> 
> Sorry  - I was not being clear.    I meant that you must have one singular process that is the agreed "official" process.   If someone decides to do something different that's ok -  provided they understand that they have to take their lumps when and if they cause a break in the main build or cause testcases to fail.     The important point I was trying to make is that the process used by contributors must always work.  In my opinion the best way to achieve that is to ensure it's in use day by day.

Ah, yes we have the "official" Release Engineering build system and tool requirements.
But it's more in the form of a list of versions and fairly controlled build systems used by Release Engineering
to perform the nightly, weekly promoted, and final product builds.

The makefiles have sanity checks to try and police these versions and will issue warning messages when what
you are using differs, and fatal sanity errors there is a high risk of a bad build or build failures given the version
of some component.

These sanity rules were relaxed quite a bit when we open sourced due to the larger variety of build systems
and compiler versions being used out there.
There is no ./configure mechanism and no 'download and install' scripts that install all the specific tools needed
to do a build, partially because solving this problem for all the Windows, Solaris, and Linux systems was not
easy. Linux is easy in this regard, Solaris a bit harder, Windows is well...  tricky. :^(

-kto