From 1a8077464042525cd2b721dbcd2cab444b7c6cbd Mon Sep 17 00:00:00 2001 From: Reinier Zwitserloot Date: Fri, 15 Sep 2023 03:42:30 +0200 Subject: [PATCH] [trivial] Updated outdated comment --- src/launch/lombok/launch/ShadowClassLoader.java | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/launch/lombok/launch/ShadowClassLoader.java b/src/launch/lombok/launch/ShadowClassLoader.java index 5f4b3afe3b..013f46e532 100644 --- a/src/launch/lombok/launch/ShadowClassLoader.java +++ b/src/launch/lombok/launch/ShadowClassLoader.java @@ -85,7 +85,8 @@ * with hot code replace and the like (this is what the {@code shadow.override} feature is for). * * - * Implementation note: {@code lombok.eclipse.agent.EclipseLoaderPatcher} relies on this class having no dependencies on any other class except the JVM boot class, notably + * Implementation note: {@code lombok.eclipse.agent.EclipseLoaderPatcher} relies on this class having no dependencies on any other class except the JVM boot class and + * package private classes inside this package explicitly listed in EclipseLoaderPatcherTransplants's {@code overrideLoadResult} (near the top). This notably * including any other classes in this package, including inner classes. So, don't write closures, anonymous inner class literals, * enums, or anything else that could cause the compilation of this file to produce more than 1 class file. In general, actually passing load control to this loader is a bit tricky * so ensure that this class has zero dependencies on anything except java core classes.