quartz api (interfaces/abstract classes) are sometimes used by users. If we shade we can't use default impl. Not blocking for me, was mainly a warning Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2013/12/3 Jean-Louis MONTEIRO <[email protected]>: > Did not get time to dig into, was just my first feeling. Could you > elaborate a bit more? > Not sure I understood the extension issue? > > JLouis > > > 2013/12/3 Romain Manni-Bucau <[email protected]> > >> The 3rd ;). The issue is we loose all quartz extensions then >> Le 3 déc. 2013 10:10, "Jean-Louis MONTEIRO" <[email protected]> a écrit : >> >> > Maybe the second (shaded) one is easier to manage at first glance. >> > So that is my preferred solution >> > >> > >> > 2013/12/3 Romain Manni-Bucau <[email protected]> >> > >> > > Ps: forgot another solutuon: shade quartz in org.apache.openejb.quartz >> > > Le 2 déc. 2013 22:23, "Romain Manni-Bucau" <[email protected]> a >> > > écrit : >> > > >> > > > Hi >> > > > >> > > > How do we handle quartz for next releases? It is very often a pain >> > > > >> > > > I propose: >> > > > 1) if in openejb loader use this one >> > > > 2) if not look for it in tomee/quartz/*.jar and create a loader with >> it >> > > > >> > > > Tomee would use 2 by default >> > > > >> > > > Wdyt? >> > > > >> > > >> > >> > >> > >> > -- >> > Jean-Louis >> > >> > > > > -- > Jean-Louis
