ppkarwasz opened a new pull request, #510: URL: https://github.com/apache/logging-flume/pull/510
## Drop `ng` from artifact names and relocate the 1.x coordinates Flume 2.0 satellites already publish their artifacts as `org.apache.flume:flume-<component>`, while the core modules still used `flume-ng-*` artifactIds and `org.apache.flume.flume-ng-*` groupIds. As a major release, 2.0.0 is the right moment to align all of them (e.g. `flume-ng-core` → `flume-core`). To keep the upgrade path smooth, the new `flume-relocations` project publishes a relocation POM at each of the 31 Flume 1.x coordinates, including those of the satellite repositories. Users who bump an old artifact to 2.0.0 are redirected to its replacement, with a warning naming the new coordinates. Other notes: - Aggregators inherit from `flume-project` and are no longer installed or deployed, so published modules inherit directly from `flume-parent`. - `flume-core-bom` (formerly `flume-dependencies`) only lists the artifacts of this repository. - Until 2.0.0 is released, the renamed modules check API compatibility against their 1.x coordinates. These overrides must be removed afterwards. - Satellites will need to switch to the new core coordinates; irc, jms and scribe also need to rename their own artifacts. 🤖 Generated with [Claude Code](https://claude.com/claude-code) -- 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]
