Hi Sounds a good idea! On Sat, 13 Jul 2019 at 04:30, Romain Manni-Bucau <[email protected]> wrote:
> Hello (again) everyone, > > Gradle shadow plugin - kind of shade plugin for gradle - forked Apache > Maven Shade ResourceTransformer to enrich it ([1]). > > By itself it is ok but I wonder if we couldn't launch a kind of abstraction > to let people code once and use the transformer - needed by libraries - in > both plugins and build tools. > > It would consist of the following parts: > > 1. Transformer API (likely something very close of our current resource > transformer), > 2. Some common transformer using 1., > 3. A generic ResourceTransformerWrapper able to instantiate a Transformer > coded with 1. and wire its lifecycle in a plain shade ResourceTransformer > (likely the same on shadow side). > > Any interest doing that here? > If so, should it be hosted in maven-shade-plugin project making it a > multi-module project? > > [1] > > https://github.com/johnrengelman/shadow/blob/master/src/main/groovy/com/github/jengelman/gradle/plugins/shadow/transformers/Transformer.groovy#L26 > > 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 > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
