jdk-sandbox: comparison jdk/make/netbeans/README

equal deleted inserted replaced

-:558b97746312
+:c496d54879f4
 provided several NetBeans projects as starting points. Below we'll
 describe how to use them, as well as how to create your own.
 Getting Started
 In addition to the source bundle for Open JDK, you'll need to download
-and install copies of the JDK and of NetBeans 6. And if you want to run
+and install copies of the JDK and of NetBeans. And if you want to run
 tests on the JDK (you do want to run tests, right?), you'll need to
 install the jtreg test harness.
 In this note, when pathnames are not fully specified, they should be
 interpreted as being relative to the directory containing this README
 "Program Files". Please be sure to install everything in a
 directories whose paths don't have any spaces!
 Downloading the JDK
 You've probably done this a million times. Download and install it
-from http://java.sun.com/javase
+from http://www.oracle.com/technetwork/java/javase/overview/index.html
 Downloading the OpenJDK sources
 Since you're reading this, d you've already downloaded the OpenJDK
 source bundle.  Later in this document we'll refer to the location
 where you installed the Open JDK sources as *install-dir*.
-Downloading a pre-built, JDK 7
+Downloading a pre-built, JDK 8
 This will be necessary to do builds of some of the projects.  In
 general, you want to download and install a pre-built JDK that
 corresponds to the OpenJDK sources you download.  Building the entire
 OpenJDK depends on a few parts of the pre-built JDK.  Get this from
-http://download.java.net/jdk7/binaries
+http://download.java.net/jdk8/binaries
 Note: For working on certain projects, like JMX and JConsole, you
-may find convenient to use a pre-built version of JDK 7 (or
+may find convenient to use a pre-built version of JDK 8 (or
 OpenJDK) rather than building your own. This will allow you
 to build only that part of the OpenJDK sources which correspond
 to that project.
-NetBeans 6
+NetBeans 7.0 or later
-Yep, NetBeans *6*. Nope, not FCS'd yet. We're on the edge here,
+Older versions may also work but are unsupported.
-enjoy it! Get the latest working development build of NetBeans 6
-from http://netbeans.org
 jtreg
 "jtreg" is the test harness for running OpenJDK's regression tests.
 Get it from http://openjdk.java.net/jtreg
 Ant
 NetBeans comes with ant, but if you use a separately-installed copy
-please make sure that it is at least version 1.7.0.
+please make sure that it is at least version 1.8.1.
 Configuring
 Building OpenJDK is hard and complex. No, strike that. While it's not
 exactly "easy", we've got it down to *relatively* small set of
 properties you need to set.
 The make.options property is for passing information about what you
 installed where to make.  Change the paths to fit your particular
 situation:
 make.options=\
-ALT_BOOTDIR=/home/me/bin/jdk1.6.0 \
+ALT_BOOTDIR=/home/me/bin/jdk1.7.0 \
-ALT_JDK_IMPORT_PATH=/home/me/bin/jdk1.7.0 \
+ALT_JDK_IMPORT_PATH=/home/me/bin/jdk1.8.0 \
 OPENJDK=true
 The trailing '\' are important, so that make gets the above as a
 single set of options.
 to read much more about building the JDK.
 Windows-specific configuration
 First, please note that the entire JDK cannot currently be built on
 Windows platforms.  This will likely limit your ability to build
 make-based projects.  See
 *install-dir*/jdk/make/README-builds.html
 for full information on issues with building on the Windows platform.
 That said, there are two ways to work with the Windows-required settings
 for the Microsoft tools. Either:
 If you use the NetBeans GUI to examine them, things are likely to not
 look "right". Please don't edit them there, please instead use a text
 editor.
 Locale Requirements
-To build the Open JDK sources, be certain that you are using the "C"
+To build the OpenJDK sources, be certain that you are using the "C"
 locale on Unix (R) platforms, or "English (United States)" locale on
 Windows.
 Platforms and architectures, oh my!
 The Open JDK can be built for a variety of operating system platforms
 JConsole (directory "jconsole")
 For working on JConsole. Creates ../dist/lib/jconsole.jar. Supports
 running and debugging JConsole.
 This ant-based project does *not* require that you build the jdk
 project first, provided that you use a pre-built version of JDK 7.
 Java (TM) Management Extensions (JMX(TM)) API (directory "jmx")
 For working on JMX source code. Creates ../dist/lib/jmx.jar.
 This ant-based project does *not* require that you build the jdk
 project first, provided that you use a pre-built version of JDK 7.
 Jar & Zip (directory "jarzip")
 For working on jar & zip. It builds the zip library (including
 native code), the jar library, and the jar tool. Creates an
 executable jar program in ../build/*platform*-*arch*/bin/jar.
 Swing (directory "swing")
 For working on Swing. Creates ../dist/lib/swing.jar. Supports
 running and debugging the SampleTree demo.
 This ant-based project does *not* require that you build the jdk
 project first, provided that you use a pre-built version of JDK 7.
 In addition, there are projects for building the compiler, javadoc,
 and related tools, in the OpenJDK langtools component.  These
 projects are separate from those described here, and have their
 own set of guidelines and conventions. For more details, see the
 README files in make/netbeans in the OpenJDK langtools component.
 Running Tests
 We use the jtreg test harness, described more fully at
 http://openjdk.java.net/jtreg
 * -build-make
 * -clean-make
 Known Issues
-Tests won't run: waiting for lock
-Occasionally when running tests, there will be a delay, followed by a
-message like this:
-Waiting to lock test result cache for
-/tmp/jdk/build/linux-i586/jtreg/jconsole/JTwork for 20 seconds
-The workaround is to stop the tests, rm -rf the offending jtreg/<project>
-directory by hand, and re-run the tests.
 Can't run nor debug a single test in the JConsole test
 In most projects, you can run a single test by opening it in the editor,
 and choosing Run File from the context menu.  If you try this with the a
 JConsole test, instead you'll see that *all* tests from *all* projects

changeset 10601	c496d54879f4
parent 7666	7b994e3dd41d