8241463: Move build tools to respective modules #2475
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a re-post of a change that was posted as webrev prior to the Github migration. It is not ready for integration as-is, since it needs to be rebased to the current HEAD, and that is bound to be a non-trivial operation after this much time.
However, I think it is relevant to have this available as a Github review, in light of the closely related JDK-8257733.
This patch will move the source code for the build tools into their respective modules, in a separate
tools
directory.Progress
Issue
Download
$ git fetch https://git.openjdk.java.net/jdk pull/2475/head:pull/2475
$ git checkout pull/2475