[7.3.0] Fix javadocs for Runfiles (bazelbuild#23058)

`Runfiles` insurance are cheap, `Preloaded` instances are costly. Closes bazelbuild#23006. PiperOrigin-RevId: 654661845 Change-Id: I46ee31718a2c5753d983b9c741547fe2a1de5d88 Commit bazelbuild@7d26615 Co-authored-by: Fabian Meumertzheim <[email protected]>
fmeum · Jul 23, 2024 · 088c517 · 088c517
1 parent 7c3c9b3
commit 088c517
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/tools/java/runfiles/Runfiles.java b/tools/java/runfiles/Runfiles.java
@@ -118,10 +118,10 @@
  * Runfiles#preload(Map)} and immutably encapsulate all data required to look up runfiles with the
  * repository mapping of any Bazel repository specified at a later time.
  *
- * <p>Creating {@link Runfiles} instances can be costly, so applications should try to create as few
- * instances as possible. {@link Runfiles#preload()}, but not {@link Runfiles#preload(Map)}, returns
- * a single global, softly cached instance of {@link Preloaded} that is constructed based on the
- * JVM's environment variables.
+ * <p>Creating {@link Preloaded} instances can be costly, so applications should try to create as
+ * few instances as possible. {@link Runfiles#preload()}, but not {@link Runfiles#preload(Map)},
+ * returns a single global, softly cached instance of {@link Preloaded} that is constructed based on
+ * the JVM's environment variables.
  *
  * <p>Instance of {@link Runfiles} are only meant to be used by code located in a single Bazel
  * repository and should not be passed around. They are created by calling {@link