Hi Tim, I was thinking of proposing this very thing over the last few weeks.
I had already deliberately pushed the CDI related spec jars and also the spec jar for JAX-RS into an aries sub-group in maven in order to better accommodate and reflect this very thing. So, I would be a big +1 for having these in a specific sub-project. - Ray On Thu, Dec 21, 2017 at 6:25 AM, Timothy Ward <[email protected]> wrote: > Hi all, > > I’ve noticed that an increasing number of Aries projects are producing > wrapped spec jars (JPA, JAX-RS, CDI...). In general I think that this is a > good thing, as few other Open Source projects package the jars with OSGi > contract metadata. > > I do wonder, however, if these spec jars should be provided by a separate > Aries project, rather than scattered across multiple other projects. I have > two main reasons for this. > > 1. It makes the code for packaging the spec jars harder to find in source > control > > 2. It creates some non-obvious links between projects. It’s clear why > tx-control depends on JPA, but not why JAX-RS depends on CDI! > > The spec jars are mostly being put into a separate Maven group already. I > would simply see this as a formalisation of that earlier decision. > > Thoughts? > > Tim > > Sent from my iPhone -- *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile> (@rotty3000) Senior Software Architect *Liferay, Inc.* <http://www.liferay.com> (@Liferay) Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org> (@OSGiAlliance)
