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
The shaded dataflow jars contain some classes that are also present in checker-qual, and classes are different for a given release. (The differences are mainly reordered constant pool entries, perhaps because the jar is processed as part of the shading process.)
Would it be possible to have the shaded dataflow jars depend on checker-qual instead of redeclaring the classes?
I noticed this because of tooling that checks classpaths to ensure that the classes are unique (or at least that duplicate classes are exactly the same), to help prevent issues from classpath version conflicts.
The shaded dataflow jars contain some classes that are also present in checker-qual, and classes are different for a given release. (The differences are mainly reordered constant pool entries, perhaps because the jar is processed as part of the shading process.)
Would it be possible to have the shaded dataflow jars depend on checker-qual instead of redeclaring the classes?
I noticed this because of tooling that checks classpaths to ensure that the classes are unique (or at least that duplicate classes are exactly the same), to help prevent issues from classpath version conflicts.
The text was updated successfully, but these errors were encountered: