loustler commented on PR #11648:
URL: https://github.com/apache/seatunnel/pull/11648#issuecomment-5378135699
@davidzollo — thanks, that settles it. I've confirmed #9993 is merged
(`4ba289595`), `seatunnel-shade/` is gone from `dev`, and the root pom now
pulls `seatunnel-shade-*` from Central via
`${seatunnel.shade.<lib>.version}-${seatunnel.shade.version}`.
The shade half of this PR is now open against the standalone repo:
**apache/seatunnel-shade#20**. It carries the two pom changes from here (Hadoop
3.4.3, AWS SDK v2 bundle filtering, SLF4J binding exclusions) and also
re-applies #11673, which #11851 asked to be resubmitted there.
That leaves this PR smaller and, usefully, no longer breaking:
- The module rename `seatunnel-hadoop3-3.1.4-uber` →
`seatunnel-hadoop3-3.4.3-uber` disappears. That artifactId no longer exists on
`dev`, and the standalone repo puts the Hadoop version in the artifact
*version* (`3.4.3-3.0.0`), not the artifactId. So does the
`incompatible-changes.md` entry that existed only to document that rename.
- What's left of the shade side is two property bumps:
`seatunnel.shade.hadoop.version` and `seatunnel.shade.hadoop-aws.version` →
`3.4.3`.
- The remaining ~85 files (connector-file-s3, connector-file-oss,
`seatunnel-dist`, `seatunnel-e2e`, checkpoint-storage-hdfs, imap-storage-file,
docs) stay here unchanged in substance.
One dependency: Central currently has only `3.1.4-2.3.13` and `3.1.4-3.0.0`
for both shade artifacts, so this PR cannot build until `3.4.3-3.0.0` is
published. I'll rebase and update it as soon as that lands — if you can give me
a rough sense of the shade release turnaround, I'll plan around it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
