Do you run with $OUTPUT/jdk (exploded classes, pre-images)?

[Paul Sandoz]

On Apr 14, 2014, at 4:01 PM, Alan Bateman <Alan.Bateman at oracle.com> wrote:

> 
> I'm interested to get a sense for how many people run/debug with the intermediate build output that is $OUTPUT/jdk. That is, the developer build that has the class files on the file system rather than images (ie: no rt.jar, no tools.jar, everything in jdk/classes on the boot class path).
> 

Almost always, unless i need to hook things up to the IDE, which does not grok the exploded JDK layout, or in the final stages of local testing.

Even so i still use a little ant script that compiles only selected packages and places the compiled classes in the right location (it can also stuff 'em in rt.jar as well if i need to patch that instead).

While there have been huge improvements to the build process i am still too impatience :-)

Paul.

> In the dark days of the old build then this was the modus operandi for many of us, partly because the images target took longer that a round trip to the coffee machine, partly because it could be combined with make -f to run specific make files for fast edit-build-debug.
> 
> The context for the question is modules where we need to figure some of the infrastructure/build changes to get us to the point where the source code is organized by module and where the build evolves to compile everything as modules. Draft JEPs coming on this soon and for now I'm just trying to get a feel for common it is to run with the intermediate output that is $OUTPUT/jdk and whether folks do anything more than run tests or just use it for debugging.
> 
> -Alan.
> 
>