I think I will go back to Maven, too. I think Gradle is appropriate to Android development, but Maven uses an more explicit syntax with xml.
Le mer. 15 juin 2022 à 20:05, John Patrick <nhoj.patr...@gmail.com> a écrit : > Looking at the Snyk Java/JVM ecosystem report 2018 vs 2021, the usage of > Maven is growing still. But yes Gradle growth also grew over the same > period. > > 2018 > - Maven 68% > - Gradle 16% > > 2021 > - Maven 76% > - Gradle 38% > > Sources; > https://snyk.io/blog/jvm-ecosystem-report-2018/ > https://snyk.io/jvm-ecosystem-report-2021/ > > Their are also several posts of people moving back to Maven after migrating > to Gradle, see; > https://phauer.com/2018/moving-back-from-gradle-to-maven/ > > Also I think build tooling is, love it or hate it. I've tried Gradle a few > times but keep coming back to Maven. You get this constantly with lots of > Languages, when will X die, when will Y replace X. Usually people doing > click bate, but after those initial posts they go quite... > > John > Maven user since 2004 > - It has issues but I prefer these issues over Gradle's. > > > On Tue, 14 Jun 2022 at 20:59, Andres Almiray <aalmi...@gmail.com> wrote: > > > Hi Manuel, welcome to the list. > > Please find answers inlined. > > > > Sent from my primitive tricorder > > > > > On 14 Jun 2022, at 20:10, Manuel Dahmen <dathew...@gmail.com> wrote: > > > > > > hello, > > > switch from maven to gradle, publish on maven central, is it possible > > from > > > maven? > > > > Yes, it’s possible to switch a project built with Maven to be built with > > Gradle instead. Both build tools offer similar capabilities yet in > > different fashions. > > > > To be fair there’s no 100% automatic, fool-proof way to translate a Maven > > project into a Gradle one due to differences in their models and how > > plugins work. You can try invoking “gradle init” at the root of your > > project then manually edit the generated Gradle files til you get wat you > > need. For this to work you need to know Gradle well. > > > > Gradle can publish artifacts to Maven Central, there are 3rd party > plugins > > that take care of that, of which the most popular appears to be > > https://plugins.gradle.org/plugin/io.github.gradle-nexus.publish-plugin > > > > > when will maven be replaced by gradle? > > > > That’s a very broad question but the answer is likely never. If the > > intention of the question is to find out if Maven will be replaced as the > > dominant build tool then the answer is no, not going to happen any time > > soon. An organization/company may deem necessary to make the switch which > > takes lots of effort, there’s no “try me” option, you must complete the > > switch to the best of your abilities in order to measure if making the > > switch was worth it. Chicken-egg problem. > > > > > I m trying to implement a Java desktop /android app. with a common > > library. > > > The basic idea is to name a class or interface wrapper with custom > > > implementations. which are not treated by jdk or Android sdk, I think. > > > But ui are custom too, like ImageIO or Bitmap, awt Color and android > > Color. > > > > If you’re building a multi-project build with at least one Android > > component then that means you must use Gradle. Why bring Maven into the > mix? > > > > > I think it s complicated, where could I find resources on this theme? > > > > Most likely at the Gradle doc site. Also, join their Slack and/or forum > to > > ask questions. > > > > > -- sorry for my poor English > > > > You’re doing great! >
