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

Tracker for ArchUnit v2

Open
#1,752 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
12/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Active
Tech stack
java
Domain
testing

Research direction

This is a maintainer tracker with no code files named, so there is no patch to start from. Read the linked issues #1753 to #1756 to see the planned breaking changes, and the release-schedule and support-policy tasks in the body. The work is a decision for maintainers about release timing (for example, waiting for Java 8 end of life) and how ArchUnit 1.x is supported. Done means those two decisions are recorded in the issue, not that code has changed.

Written by the indexing model from the issue text.

Description

breaking change

This is a meta-issue to keep track of ideas and plans that require a breaking change. As of this writing, there are no concrete plans for releasing ArchUnit v2 yet.

Tasks

  • Decide on a release schedule (do we want to e.g. wait for Java 8 EOL?)
  • Decide on a support concept for ArchUnit 1.x (e.g.: deprecate / maintenance mode / feature parity within reason)

Ideas, Features, Changes

(other maintainers: feel free to edit and update this post as appropriate)

Dominant language
Java
Stars
3.9k
Forks
350
Avg merge
1d 20h
Merged PRs (30d)
22

Getting set up

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 TNG/ArchUnit

All issues in TNG/ArchUnit

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.