Skip to content

MCR-3462 Classpath usually only needs to be determined once #2603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

toKrause
Copy link
Contributor

@toKrause toKrause changed the title MCR-3462 Classpath usualy only needs to be determined once MCR-3462 Classpath usually only needs to be determined once Jul 31, 2025
@toKrause toKrause force-pushed the issues/MCR-3462_Classpath-only-needs-to-be-determined-once-2 branch 3 times, most recently from 16ff388 to d871025 Compare August 1, 2025 09:00
…ath dirs

By default, use system property java.class.path to obtain list of classpath dirs.
This search is only performed once, since this property won't change during the
runtime of the application. This is usualy sufficient.

If an application adds classpath dirs to the classloader at runtime, the former strategy,
that scanned the class loader for classpath entries each time, might still be needed.
The former startegy is still available and can be selected, if required.

For this, a new interface, MCRClasspathDirsProvider, and a new hint, CLASSPATH_DIRS_PROVIDER,
is added. The inetrface abstracts the strategy to obtain classpath dirs, the hint
provides the selected implementation to all resource related components.
@toKrause toKrause force-pushed the issues/MCR-3462_Classpath-only-needs-to-be-determined-once-2 branch from d871025 to d52c039 Compare August 5, 2025 22:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant