Skip to content

Look into deprecating the legacy archunit-junit public package #1663

Description

@schulzjo-tng

The legacy archunit-junit package has been moved to archunit-junit4 many years ago, but the metadata do not show that in a way that the Maven Repository acknowledges this. Such a feature is supported, see e.g. https://mvnrepository.com/artifact/com.gradle/gradle-enterprise-maven-extension:

Image

All we might need is a block in the pom.xml like so:

<distributionManagement>
  <relocation>
    <artifactId>archunit-junit4</artifactId>
  </relocation>
</distributionManagement>

see e.g. this manual and the pom.xml of the gradle-enterprise-maven-extension linked above.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions