Just curious - is it possible to 'extend' jvm.config? I always run into this when we update versions - we add changes to this file over time and Adobe makes changes and it's always a pain to figure what's new, what we need to keep, etc. Would be nice if I could extend it to include only my changes... something like adobe.args and customer.args which later just get concatenated into java.args...

Not sure if possible but I love the idea you are pitching here!

@Jim Priest I will take this forward and ask if that is possible. I like the idea and see if this can be implemented. I cannot commit but will ensure that it reaches the right folks in our team

Thanks @priyank_adobe!!! Java 17 also seems much more locked down - have run into a few things that worked in Java 11 but 17 is complaining about. Digging into the --add-exports and --add-opens flags ... I noticed in the 2023 jvm.config there are a lot more of these 🙂