apache / apache/doris-flink-connector
[Bug] invalid maven metadata for 1.4.0 release
- Dominant language
- Java
- Stars
- 385
- Forks
- 279
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 6
Description
### Search before asking
- [X] I had searched in the [issues](https://github.com/apache/incubator-doris/issues?q=is%3Aissue) and found no similar issues.
### Version
1.4.0
### What's Wrong?
The metadata on maven central is incorrect. If you look at https://search.maven.org/artifact/org.apache.doris/flink-doris-connector-1.17/1.4.0/jar the metadata file contains `1.4.0-SNAPSHOT` and `${revision}`.
In previous releases it appears there was `1.3.0` and no `` tag.
### What You Expected?
`1.4.0-SNAPSHOT` should be `1.4.0`, or there should be no `` tag and `` should be set to 1.4.0.
### How to Reproduce?
Add flink-doris-connector dependency to your project, per https://search.maven.org/artifact/org.apache.doris/flink-doris-connector-1.17/1.4.0/jar.
For example `implementation("org.apache.doris:flink-doris-connector-1.17:1.4.0")` if using gradle kotlin DSL.
The build fails because the metadata is inconsistent:
```
> Could not resolve org.apache.doris:flink-doris-connector-1.17:1.4.0.
> inconsistent module metadata found. Descriptor: org.apache.doris:flink-doris-connector-1.17:1.4.0-SNAPSHOT Errors: bad version: expected='1.4.0' found='1.4.0-SNAPSHOT'
```
### Anything Else?
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of Conduct](https://www.apache.org/foundation/policies/conduct)
Contributor guide
Research direction
No source file or test is identified. Reproduce the failure with the Gradle Kotlin DSL dependency on org.apache.doris:flink-doris-connector-1.17:1.4.0, then inspect the published Maven metadata for that artifact and the release or publishing configuration that generated it. Done means the 1.4.0 metadata resolves without an inconsistent-module error and reports version 1.4.0.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100