JDK 7 build 24 is available at the openjdk.java.net website
Brad Wetmore
Bradford.Wetmore at Sun.COM
Wed Jan 9 03:21:46 UTC 2008
Climbing back up on the dead horse: (that is: I am now back from vacation)
>> The key is in getting the Mercurial with the forest extension
>> installed--I
>> had 0.9.5, which didn't, and I couldn't figure out where to get it or
>> how to
>> install it;
I simply got the 0.9.4 version from:
http://www.selenic.com/mercurial/wiki/index.cgi/BinaryPackages
and then cloned hgforest from the source, copied the .py file right into
the c:/Mercurial directory and pointed my .hgrc file to it. No
"batteriesrequired" distribution.
What *WASN'T* immediately obvious to me is that there was no hgmerge
file in these distributions. It makes some sense, given that the
standard hgmerge file is a UNIX sh script, but since I'm using MKS...
At least on my system, this file *HAD* to be called "hgmerge.sh". If it
was "hgmerge", it would expect a DOS batch file, and thus wouldn't run.
So I simply copied over the UNIX hgmerge into:
c:/Mercurial/hgmerge.sh
tweaked the PATH variable to reflect the various locations of my diff
programs, and let it go.
I'm sure there will be more info on this soon, but something else you
should be aware of working on windows: the "CR-LF" issue. OpenJDK has
standardized on the Unix end-of-line ("LF") style. I know some windows
editors can be set to only write a "LF", but most editors insert the
"CR", which means you will need to strip these before the new changeset
checker will accept them.
MKS has flip(1), others have dos2unix(1)...
The reason for this requirement is because if a Unix changeset follows a
Windows changeset, Mercurial will happily store two complete versions of
the file, rather than just the deltas.
Brad
More information about the build-dev
mailing list