Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

declarative script plugin dependencies

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

Start with the issue's draft API and inspect the Gradle script-plugin entry points that handle plugin application order. Trace how script plugins are applied and how violations could be reported. Done means the proposed dependency relationships are declarative and produce clear errors for invalid ordering, exclusivity, and future application cases.

Written by the indexing model from the issue text.

Description

enhancement pr-welcome

It is common that script plugins will need to be applied in a specific order. It would be nice if these scripts gave nice declarative error messages if this was violated. Here is a draft API:

/**
  * Throws an error if `('base/java')` hasn't already been applied.
  * (Must be called only from within a script plugin.)
  */
void 干.requires('base/java') { ... }

/**
  * Throws an error if `('base/scala')` has been applied,
  * or if it is applied in the future.
  * (Must be called only from within a script plugin.)
  */
void 干.mutuallyExclusiveWith('base/scala') { ... }

/**
  * If `base/java` has already been applied, or is never applied, then this is fine.
  * But if `base/java` is ever applied in the future, then there will be an error,
  * because this plugin must run after 'base/java'.
  * (Must be called only from within a script plugin.)
  */
void 干.mustRunAfter('base/java') { ... }

void 干.mustRunBefore('base/java') { ... }
Dominant language
Java
Stars
29
Forks
6
Avg merge
8m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from diffplug/blowdryer

All issues in diffplug/blowdryer

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.