Hey Stephen,
Others can correct my points but from what I remember initial setup was
based on gradle due to its flexibility.
Since many things get promoted via Maven Central and Maven is still far
more popular for traditional development [1], obvious choice was to
introduce better support for Maven and stay open towards this side of
the community.
Since Maven is also less flexible than Gradle it is less likely it will
blow things up. The fewer surprises user can spot during his first steps
the better experience he gets as a newcomer.
I would abstain from discussion which tool is better. At the time
decision was made Maven was more popular than Gradle.
These days you can create Maven based builds and they are fully
supported either via bnd-maven-plugin(s) or former maven-bundle-plugin
provided by Apache Felix project.
[1] One of stats from 2019 shows 60% for Maven versus 19% for Gradle:
Maven https://snyk.io/blog/jvm-ecosystem-report-2018-tools/
Kind regards,
Łukasz Dywicki
--
Code-House http://code-house.org
On 24.06.2019 22:28, Stephen Schaub via osgi-dev wrote:
> I'm new to OSGi and am starting a project. I found the enRoute material
> and noticed that the enRoute tutorials apparently at one time utilized
> Gradle as the build tool, but are now using Maven.
>
> I'm more familiar with Gradle and have worked out how to use Gradle to
> do what I need for the project, but I was wondering 1) why the switch
> from Gradle to Maven for enRoute and 2) is Maven the preferred build
> tool for OSGi going forward? Is there a reason I should consider
> switching to Maven?
>
> I've poked through the mailing list archives trying to find answers to
> these questions but can't seem to find a record of any discussions about
> this, so am hoping someone can shed some light for me.
>
> --
> Stephen Schaub
>
> ___
> OSGi Developer Mail List
> osgi-dev@mail.osgi.org
> https://mail.osgi.org/mailman/listinfo/osgi-dev
>
___
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
