You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
hash is calculated during jar scanning,
before was calculated during class compare
which cause to open and read jars again - now jar is opened once
close#122
hash is calculated during jar scanning,
before was calculated during class compare
which cause to open and read jars again - now jar is opened once
close#122
We have a large Dependency with some big dependencies. The check for BanDuplicateClasses tooks over 10 minutes. The check consume the most time in
extra-enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer/Hasher.java
Line 101 in 149c131
Is it possible to optimize this behavior? I think to cache the JAR could help instead of to read the JAR for each file again.
The text was updated successfully, but these errors were encountered: