Maven should not filter out non-jrt URLs from Java platform modular BCP.

[lahodaj]

When computing module boot path, the Maven provider filters out URLs that are not nbjrt URLs. That does not make much sense to me, and it does not work for exploded JDK builds (which have classfiles in directories on the filesystem, not in the JRT file system).

I propose to simply use whatever bootstrap libraries the platform provides, and not filter them.

[mbien]

adding platform and maven tests and restarting CI

[mbien]

how do you add the exploded folder as JDK? I believe the only thing which worked for me in past was to add the image output in jdk/build/linux-x86_64-server-release/images/jdk

[lahodaj]

how do you add the exploded folder as JDK? I believe the only thing which worked for me in past was to add the image output in jdk/build/linux-x86_64-server-release/images/jdk

Sorry, I missed the question. Adding ${build-dir}/jdk should work, and that's the exploded build. I.e. in your case jdk/build/linux-x86_64-server-release/jdk.

[mbien]

@lahodaj we could merge this too. Please rebase till Wednesday.

[lahodaj]

OK to merge?

[mbien]

we can try. Its small so it would be easy to revert if something shows up during RC.