On 6 February 2018 at 06:08, Romain Manni-Bucau <[email protected]> wrote:
> I do and it works in several cases but it is a lot of work to handle the > classloader right and found several plugins just broken cause they use a > parent first strategy. This API being so easily pulled - spring/jaxrs can > easily pull it - it shouldnt sit here by default IMHO. > > Dont think there is a ticket yet but would like to know if dropping it is > an option? Not sure if guice+api should be shaded or equivalent. > could be solved easily by changing lines here https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/maven/extension.xml#L95 but I guess this "simple" change could/will have a LOT of impacts :-( > > Le 5 févr. 2018 23:52, "Tibor Digana" <[email protected]> a écrit : > > > This must be a big problem for you actually. > > Can you use isolated ClassLoader, set Context ClassLoader in current > Thread > > and back the origin, reflectively create a new instance of a factory and > > build an object which runs your code during the plugin execution? When > the > > plugin's job has finally finished replace CL in current Thread. > > > > On Fri, Jan 19, 2018 at 1:18 PM, Romain Manni-Bucau < > [email protected] > > > > > wrote: > > > > > Hi guys, > > > > > > cdi-api is still in maven lib and breaks any plugin using it since it > is > > an > > > old version, can it be dropped or at least isolated from plugin > > > classloaders? > > > > > > Thanks, > > > 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> > > > > > > -- Olivier Lamy http://twitter.com/olamy | http://linkedin.com/in/olamy
