cabaletta/baritone

Build process should clear build/libs after finishing creating dist/

Open

#325 opened on Feb 1, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (1,380 forks)batch import
enhancementgood first issue

Repository metrics

Stars
 (6,154 stars)
PR merge metrics
 (Avg merge 121d 14h) (9 merged PRs in 30d)

Description

So that people aren't confused and use the pre proguard jar. build/libs is a standard place to look, and there is a jar there that looks like the valid build result, however that jar shouldn't be used, so it should ideally be deleted after completion. Could be added to ProguardTask.cleanup or similar.

Contributor guide

Research direction
Examine the ProguardTask in the Gradle build script and add a cleanup step to delete the build/libs directory after the dist/ is created.
Tech stack
java
Domain
build system
Issue type
Chore
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.
Under 1 hour
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
Gradle
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70