Maven Shade and MSHADE-352 (timestamp support), mitigate the breaking change of last release

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

Maven Shade and MSHADE-352 (timestamp support), mitigate the breaking change of last release

Romain Manni-Bucau
Hi everyone,

Wonder if we can't mitigate the breaking change in the last minor of shade
plugin (due to MSHADE-352).

Idea would be to have a TimeAwareResourceTransformer extends
ResourceTransformer and handle an instanceof or equivalent in our codebase
to avoid to break all transformers outside maven-shade project.

Wdyt?

Romain Manni-Bucau
@rmannibucau <https://twitter.com/rmannibucau> |  Blog
<https://rmannibucau.metawerx.net/> | Old Blog
<http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> |
LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
<https://www.packtpub.com/application-development/java-ee-8-high-performance>