quarkusio/quarkus

Separate Gradle getting started from the Maven one

Open

#2,090 opened on Apr 15, 2019

View on GitHubContributor guide
 (15 comments) (0 reactions) (0 assignees)Java (2,464 forks)batch import
area/gradlegood first issuetriage/gsmet-christmas-list

Repository metrics

Stars
 (12,967 stars)
PR merge metrics
 (Avg merge 6d 4h) (325 merged PRs in 30d)

Description

(Creating the issue here so that it gets some visibility for new contributors)

Currently, the getting started project for Gradle in https://github.com/quarkusio/quarkus-quickstarts/ is the same as the Maven getting started.

This is a mistake as the project structure should be different (especially the unit tests and the integration tests should be in 2 different folders).

We need to create a specific project for Gradle and get rid of the Gradle files in the getting-started project.

The project should be built with the Gradle command line.

Note to self: we will need to upgrade the release scripts once it's done.

Contributor guide

Research direction
Study the existing getting started project structure, identify all Gradle related files, create a separate Gradle project with proper unit and integration test directory structure, and update release scripts accordingly.
Tech stack
java
Domain
build system
Issue type
Refactor
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaGradleGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75