You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@polaris.apache.org by Yong Zheng <yz...@apache.org> on 2025/07/11 05:27:43 UTC

Use Makefile to simplify setup and command

Right now, getting set up or performing routine builds often means jumping between different documentation pages to find various tool installations (like helm, kubectl, jq, jenv, git, docker) and then copying lengthy gradlew commands. While it makes sense to have granular instructions for deep dives or specific contributions, having a single, straightforward entry point for common tasks could really smooth out onboarding for new folks and make our development flow much more efficient (copied from PR summary).

Here is the sample PR: https://github.com/apache/polaris/pull/2027

Re: Use Makefile to simplify setup and command

Posted by Yong Zheng <yz...@apache.org>.
Added.

Thanks,
Yong Zheng

On 2025/07/18 21:18:13 Dmitri Bourlatchkov wrote:
> Adding a helper Makefile, as Yong proposed, SGTM.
> 
> It would be nice to have README notes to clarify its relationship to
> Gradle, though (also commented in GH).
> 
> Thanks,
> Dmitri.
> 
> On Fri, Jul 11, 2025 at 1:27 AM Yong Zheng <yz...@apache.org> wrote:
> 
> > Right now, getting set up or performing routine builds often means jumping
> > between different documentation pages to find various tool installations
> > (like helm, kubectl, jq, jenv, git, docker) and then copying lengthy
> > gradlew commands. While it makes sense to have granular instructions for
> > deep dives or specific contributions, having a single, straightforward
> > entry point for common tasks could really smooth out onboarding for new
> > folks and make our development flow much more efficient (copied from PR
> > summary).
> >
> > Here is the sample PR: https://github.com/apache/polaris/pull/2027
> >
>

Re: Use Makefile to simplify setup and command

Posted by Dmitri Bourlatchkov <di...@apache.org>.
Adding a helper Makefile, as Yong proposed, SGTM.

It would be nice to have README notes to clarify its relationship to
Gradle, though (also commented in GH).

Thanks,
Dmitri.

On Fri, Jul 11, 2025 at 1:27 AM Yong Zheng <yz...@apache.org> wrote:

> Right now, getting set up or performing routine builds often means jumping
> between different documentation pages to find various tool installations
> (like helm, kubectl, jq, jenv, git, docker) and then copying lengthy
> gradlew commands. While it makes sense to have granular instructions for
> deep dives or specific contributions, having a single, straightforward
> entry point for common tasks could really smooth out onboarding for new
> folks and make our development flow much more efficient (copied from PR
> summary).
>
> Here is the sample PR: https://github.com/apache/polaris/pull/2027
>