Hi Stephen,
1. Maven is very popular. So using maven makes it easy for a large
audience to adopt OSGi. When there is an integration for the right build
tool, people tend to rather try things out, then if they have to "learn"
a new build tool.
2. You can also use gradle. We use only gradle together with bnd for the
OSGi development in all our projects. Just try the Eclipse bndtools out.
It creates a workspace utilizing gradle.
Mark
Am 24.06.19 um 22:28 schrieb Stephen Schaub via osgi-dev:
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
--
Mark Hoffmann
M.A. Dipl.-Betriebswirt (FH)
CEO/CTO
Phone: +49 3641 384 910 0
Mobile: +49 175 701 2201
E-Mail: m.hoffm...@data-in-motion.biz
Web: www.datainmotion.de
Data In Motion Consulting GmbH
Kahlaische Strasse 4
07745 Jena
Germany
Geschäftsführer/CEO
Mark Hoffmann
Jürgen Albert
Jena HRB 513025
Steuernummer 162/107/05779
USt-Id DE310002614
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev