The build will create debuginfo/diz files as requested - that's fine.
What I'm unclear about is where those files should actually appear in
our build artifacts, specifically the jdk/jre images that are created.
Internally when we create binary images RE strips all the debuginfo/diz
files out. But the build itself seems to treat them in an ad-hoc manner:
- The new build deliberately excludes debuginfo/diz files associated
with binaries, but will include any related to libraries (via generic
copying routine). (It's obvious from the comments related to this that
there is some puzzlement as to this reasoning.)
- The old build also tries to exclude the files associated with
binaries, but only handles .debuginfo not .diz :( Those associated with
libraries just seem to get copied if they happen to be there
As I said this all seems very ad-hoc to me. I would expect to see no
debuginfo/diz files in a created image by default, and have a separate
target that would produce a tar file of all the debuginfo/diz files
ready to overlay on an existing image.
Thoughts/comments?
I have to deal with this for the SE Profile work, where we will not want
these files present in any of the images.
David
