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
Currently, JVM's Jar task responsible for generating executable benchmarks jar generates a brand new manifest that includes only a main-class attribute.
Depending on shaded libraries, that might be an issue. For example, if one of the libraries bundled into a resulting jar was a MR-JAR, the resulting manifest will be missing multi-release: true attribute and target-specific code will never be invoked (and that's a problem if you're actually trying to benchmark MR-related functionality ;) ).
It would be nice to merge manifests when generating a jar, like Maven Shade's AppendingTransformer does.
The text was updated successfully, but these errors were encountered:
Currently, JVM's Jar task responsible for generating executable benchmarks jar generates a brand new manifest that includes only a main-class attribute.
Depending on shaded libraries, that might be an issue. For example, if one of the libraries bundled into a resulting jar was a MR-JAR, the resulting manifest will be missing
multi-release: true
attribute and target-specific code will never be invoked (and that's a problem if you're actually trying to benchmark MR-related functionality ;) ).It would be nice to merge manifests when generating a jar, like Maven Shade's
AppendingTransformer
does.The text was updated successfully, but these errors were encountered: