I'm not aware of any gradle build in any of the Aries components, so Maven
would definitely be more uniform.
Also, by using maven you can easily, almost without effort, hook into some
plugins are set up in the aries/apache parent poms to do additional
checking, such as the license checking done by the RAT plugin.
So personally I think it would nice if the JAX-RS component could use Maven
to build, but I don't think it's a definite requirement.
On 11 October 2016 at 19:10, Raymond Auge <raymond.a...@liferay.com> wrote:
> Hello everyone,
> We're getting closer (slower than anticipated) to bootstrap Aries with the
> RFC-217 impl.
> I'd like to ask about project structure. Currently we've got a gradle
> based build. Does Aries require the build to be maven?
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>