testcontainers / testcontainers/testcontainers-java
[Enhancement]: Deploy relocation artifacts
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 8.7k
- Forks
- 1.9k
- Avg merge
- 2d 17h
- Merged PRs (30d)
- 9
Description
Module
All now prefixed with testcontainers-
Proposal
As of version 2 all artifacts have been relocated/prefixed with testcontainers-.
The old artifacts (without testcontainers-) will however not receive automatic dependency updates with a notice that these have been renamed.
This should be fixed by deploying empty v2 artifacts that have a relocation section.
Here's an example repo how we deploy our relocation artifacts: https://github.com/xdev-software/maven-redirector
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the maven-redirector example linked in the proposal and locate this repository's artifact publication configuration. Define the old artifact coordinates that need relocation and verify that each deployed v2 artifact contains a relocation section and produces the intended rename notice during dependency updates.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100