Re: Why migrate from Maven to Gradle
Il Mar 16 Giu 2020, 05:31 Haisheng Yuan ha scritto: > Hi Zoltan, > > > For example I use NetBeans, and things just work with maven. > Hi If you use NetBeans 11.3+ you can open Calcite again. Better 12.0 Enrico Have you tried intellij? It works fine with Gradle. And it is free. > > > Gradle will add friction to contributors familiar with maven and > unfamiliar with gradle... > Your case is far better than mine, at least you have knowledge of maven. I > have near 0 knowledge for both maven and gradle. But that doesn't prevent > me from making contribution to Calcite. The only command I run daily is > ./gradlew build. And I am happy with it. :) So don't worry about that. > Feel free to ask if you need help, I think Vladimir and other community > members are more than happy to help. > > Thanks, > Haisheng > > On 2020/06/15 23:27:21, Zoltan Farkas > wrote: > > Vladimir, > > > > A new user will probably be impacted more by the IDE experience. > > > > Some IDEs do better at handling maven than gradle... For example I use > NetBeans, and things just work with maven. > > > > In my experience, Maven is simply a more mature tool (use it since > 2002), more plugins, good IDE support, with more developers being fluent > with it. > > > > Gradle will add friction to contributors familiar with maven and > unfamiliar with gradle... > > > > Hope it’s worth it... > > > > --z > > > > > On Jun 15, 2020, at 2:49 PM, Vladimir Sitnikov < > sitnikov.vladi...@gmail.com> wrote: > > > > > > > > >> > > >> Gradle is not that user friendly for new uses > > > > > > Can you please elaborate? > > > > > > Gradle's command line is easier to follow as it provides help with the > > > usable tasks and descriptions, > > > and it requires much less ceremony. > > > For instance, with Maven I often had issues like > "ExtenderSqlParserImpl not > > > found" (== I had to build the project before importing to the IDE), > > > and Gradle fixes that. > > > > > > Vladimir > > > > >
Re: Why migrate from Maven to Gradle
Hi Zoltan, > For example I use NetBeans, and things just work with maven. Have you tried intellij? It works fine with Gradle. And it is free. > Gradle will add friction to contributors familiar with maven and unfamiliar > with gradle... Your case is far better than mine, at least you have knowledge of maven. I have near 0 knowledge for both maven and gradle. But that doesn't prevent me from making contribution to Calcite. The only command I run daily is ./gradlew build. And I am happy with it. :) So don't worry about that. Feel free to ask if you need help, I think Vladimir and other community members are more than happy to help. Thanks, Haisheng On 2020/06/15 23:27:21, Zoltan Farkas wrote: > Vladimir, > > A new user will probably be impacted more by the IDE experience. > > Some IDEs do better at handling maven than gradle... For example I use > NetBeans, and things just work with maven. > > In my experience, Maven is simply a more mature tool (use it since 2002), > more plugins, good IDE support, with more developers being fluent with it. > > Gradle will add friction to contributors familiar with maven and unfamiliar > with gradle... > > Hope it’s worth it... > > --z > > > On Jun 15, 2020, at 2:49 PM, Vladimir Sitnikov > > wrote: > > > > > >> > >> Gradle is not that user friendly for new uses > > > > Can you please elaborate? > > > > Gradle's command line is easier to follow as it provides help with the > > usable tasks and descriptions, > > and it requires much less ceremony. > > For instance, with Maven I often had issues like "ExtenderSqlParserImpl not > > found" (== I had to build the project before importing to the IDE), > > and Gradle fixes that. > > > > Vladimir > >
Re: Why migrate from Maven to Gradle
Vladimir, A new user will probably be impacted more by the IDE experience. Some IDEs do better at handling maven than gradle... For example I use NetBeans, and things just work with maven. In my experience, Maven is simply a more mature tool (use it since 2002), more plugins, good IDE support, with more developers being fluent with it. Gradle will add friction to contributors familiar with maven and unfamiliar with gradle... Hope it’s worth it... --z > On Jun 15, 2020, at 2:49 PM, Vladimir Sitnikov > wrote: > > >> >> Gradle is not that user friendly for new uses > > Can you please elaborate? > > Gradle's command line is easier to follow as it provides help with the > usable tasks and descriptions, > and it requires much less ceremony. > For instance, with Maven I often had issues like "ExtenderSqlParserImpl not > found" (== I had to build the project before importing to the IDE), > and Gradle fixes that. > > Vladimir
Re: Why migrate from Maven to Gradle
>Gradle is not that user friendly for new uses Can you please elaborate? Gradle's command line is easier to follow as it provides help with the usable tasks and descriptions, and it requires much less ceremony. For instance, with Maven I often had issues like "ExtenderSqlParserImpl not found" (== I had to build the project before importing to the IDE), and Gradle fixes that. Vladimir
Re: Why migrate from Maven to Gradle
Thanks, are there some building functionalities that grade can do but maven can not ? Gradle is not that user friendly for new uses but I works well, it has better flexibility than maven with many custom plugins. Best, Danny Chan 在 2020年6月13日 +0800 AM1:31，丁小冬(比古) ，写道： > > Hi, Calcite developers > > I would like to build calcite with Maven, but now calcite only support gradle > build. I have three questions: > 1. Is there any reason that Calcite had to migrate from maven to gradle? > 2. If I still insist on using maven to build calcite, is there any risk? > 3. If I want to migrate from gradle back to maven, is there any quick and > correct method to do this? > > thank you for your attention, this is really important to me, looking forward > to your reply > > Great thanks > Winter Ding
Re: Why migrate from Maven to Gradle
>2. If I still insist on using maven to build calcite, is there any risk? >3. If I want to migrate from gradle back to maven, is there any quick and correct method to do this? Calcite should have dropped Maven support. So if you want to use Maven somehow, it 1) won't be in Calcite repo 2) you might work it around in your own fork. Additional question: why do you want to migrate back to Maven? -Rui On Fri, Jun 12, 2020 at 11:07 AM Rui Wang wrote: > This email thread contains some discussions: > https://lists.apache.org/thread.html/d43cf9958613c2b7489860d076f2d714551c1002f6fd41fd1f5c6e18%40%3Cdev.calcite.apache.org%3E > > > -Rui > > On Fri, Jun 12, 2020 at 10:31 AM 丁小冬(比古) > wrote: > >> >> Hi, Calcite developers >> >> I would like to build calcite with Maven, but now calcite only support >> gradle build. I have three questions: >> 1. Is there any reason that Calcite had to migrate from maven to gradle? >> 2. If I still insist on using maven to build calcite, is there any risk? >> 3. If I want to migrate from gradle back to maven, is there any quick and >> correct method to do this? >> >> thank you for your attention, this is really important to me, looking >> forward to your reply >> >> Great thanks >> Winter Ding > >
Re: Why migrate from Maven to Gradle
This email thread contains some discussions: https://lists.apache.org/thread.html/d43cf9958613c2b7489860d076f2d714551c1002f6fd41fd1f5c6e18%40%3Cdev.calcite.apache.org%3E -Rui On Fri, Jun 12, 2020 at 10:31 AM 丁小冬(比古) wrote: > > Hi, Calcite developers > > I would like to build calcite with Maven, but now calcite only support > gradle build. I have three questions: > 1. Is there any reason that Calcite had to migrate from maven to gradle? > 2. If I still insist on using maven to build calcite, is there any risk? > 3. If I want to migrate from gradle back to maven, is there any quick and > correct method to do this? > > thank you for your attention, this is really important to me, looking > forward to your reply > > Great thanks > Winter Ding
Why migrate from Maven to Gradle
Hi, Calcite developers I would like to build calcite with Maven, but now calcite only support gradle build. I have three questions: 1. Is there any reason that Calcite had to migrate from maven to gradle? 2. If I still insist on using maven to build calcite, is there any risk? 3. If I want to migrate from gradle back to maven, is there any quick and correct method to do this? thank you for your attention, this is really important to me, looking forward to your reply Great thanks Winter Ding
