On Wed, 12 Mar 2025 20:07:21 GMT, Severin Gehwolf <sgehw...@openjdk.org> wrote:
> > What happens with the local debugging experience in the exploded image if > > you configure with ` --with-external-symbols-in-bundles=public`? > > Do we care about the local debugging experience in that case? I'd argue if > good debug experience is what is wanted, you'd omit > `--with-external-symbols-in-bundles=public` configure option? I think this can easily be turned around as, do we care about being able to run certain tests using the image in the build directory, rather than using an unpacked bundle, which is what we are actually shipping? The underlying issue here is that the image we produce in the build output directory isn't exactly what we then bundle up and ship. The image is trying to serve multiple purposes and compromises were made a long time ago which we are still carrying today. I'm not sure what the right answer is. We have contemplated enabling `--with-external-symbols-in-bundles=public` for Oracle builds, but with this change, I think it would be a lot less likely to happen, because JDK developers would have to actively opt out of it if we made it default for us. ------------- PR Comment: https://git.openjdk.org/jdk/pull/24012#issuecomment-2719078009
