testcontainers / testcontainers/testcontainers-jooq-codegen-maven-plugin
Not properly declaring dependencies
Open
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 70
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
Description
Maven project that uses testcontainers-jooq-codegen-maven-plugin always print a WARNING
Steps to Reproduce
- Add testcontainers-jooq-codegen-maven-plugin to your project
<build>
<plugins>
<plugin>
<groupId>org.testcontainers</groupId>
<artifactId>testcontainers-jooq-codegen-maven-plugin</artifactId>
<version>0.0.4</version>
...
</plugin>
</plugins>
</build>
- Build your project
./mvnw clean verify -Dmaven.plugin.validation=VERBOSE
- See Warning in build log (console)
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 31.246 s
[INFO] Finished at: 2025-04-06T13:36:26+02:00
[INFO] ------------------------------------------------------------------------
[WARNING]
[WARNING] Plugin validation issues were detected in 1 plugin(s)
[WARNING]
[WARNING] * org.testcontainers:testcontainers-jooq-codegen-maven-plugin:0.0.4
[WARNING] Declared at location(s):
[WARNING] * bitxon:spring-jooq-postgres:0.0.1-SNAPSHOT (pom.xml) @ line 93
[WARNING] Used in module(s):
[WARNING] * bitxon:spring-jooq-postgres:0.0.1-SNAPSHOT (pom.xml)
[WARNING] Plugin issue(s):
[WARNING] * Plugin should declare these Maven artifacts in `provided` scope: [org.apache.maven:maven-builder-support:3.9.0, org.apache.maven:maven-model-builder:3.9.0, org.apache.maven:maven-core:3.9.0, org.apache.maven:maven-repository-metadata:3.9.0, org.apache.maven:maven-plugin-api:3.9.0, org.apache.maven:maven-resolver-provider:3.9.0, org.apache.maven:maven-settings:3.9.0, org.apache.maven:maven-artifact:3.9.0, org.apache.maven:maven-model:3.9.0, org.apache.maven:maven-settings-builder:3.9.0]
[WARNING]
[WARNING]
[WARNING] Fix reported issues by adjusting plugin configuration or by upgrading above listed plugins. If no upgrade available, please notify plugin maintainers about reported issues.
[WARNING] For more or less details, use 'maven.plugin.validation' property with one of the values (case insensitive): [BRIEF, DEFAULT, VERBOSE]
[WARNING]
Contributor guide
No contributing guide indexed for this repository
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
The warning appears when building the Maven project configured in pom.xml; start by reviewing the plugin's declared Maven dependencies against the artifacts listed in the report. Run ./mvnw clean verify -Dmaven.plugin.validation=VERBOSE and consider the issue done when plugin validation no longer reports those dependencies.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100