Well the issue is they depend on openejb or tomee. Typically today the interesting plugins (not the scan.xml or jee5 -> jee6 ones) can't be released without releasing openejb and tomee.
- Romain Le 25 juin 2012 04:36, "Stephen Connolly" <[email protected]> a écrit : > You are better off pulling the maven plugins out, as a maven plugin cannot > be consumed within the reactor that produces it (ie if there is a full GAV > match V being critical) > > On Sunday, 24 June 2012, David Blevins wrote: > > > > > On Jun 22, 2012, at 6:07 AM, Jean-Louis MONTEIRO wrote: > > > > > IMHO, we could get out and get different life cycle for: > > > Arquillian > > > OSGi > > > TomEE > > > Maven > > > Examples? > > > > We pulled out javaee-api and that went well. I suggest we take the > simple > > approach and try one more. Getting the CI setup in order is the tricky > > part. The pulling is the easy part. We probably don't want to pull now > > and work out the details of the CI system later as then we'll have some > bad > > breakage on our hands. > > > > I had intended to spend the weekend working on the CI stuff but got side > > tracked with the anonymous website editing features of CMS which are > > probably way more important -- we even have committers who don't know how > > to update the side, so lot's needs to be improved with that process. > > > > Anyway, maybe Maven plugins could individually be pulled out. Each > plugin > > could be independently released and versioned. > > > > > > -David > > > > >
