build: introduce aggregator modules and unify pom display names#8541
Open
build: introduce aggregator modules and unify pom display names#8541
Conversation
The storm-multilang/, storm-dist/, external/ and examples/ trees previously listed their children directly in the root pom (or its profiles) without an aggregator pom of their own, which broke the standard Maven multi-module shape (no `mvn -pl <group> -am` builds, no shared parent for grouped concerns) and made the root module list noisy. Pom display names were also inconsistent or missing across the tree. - Add aggregator poms: storm-multilang/pom.xml (storm-multilang), storm-dist/pom.xml (storm-dist), external/pom.xml (storm-external), examples/pom.xml (storm-examples). All four use packaging=pom and inherit from the storm root. - Repoint each child under those trees to its new aggregator parent (relativePath ../pom.xml). storm-dist/binary and storm-dist/source likewise declare storm-dist as parent. Children's own artifactId/groupId are not changed. - Collapse the root pom <modules> and the dist/externals/examples profiles to one entry per group (storm-multilang, storm-dist, external, examples). Profile activation semantics are preserved (externals and examples remain activeByDefault). - Normalize <name> across every pom to "Storm <Module>" (e.g. "Storm Client", "Storm Flux Core", "Storm Multilang JavaScript", "Storm Kafka Client", "Storm Starter"). Removes the mix of artifact-style lowercase names, "Apache Storm - X", developer-name false positives in poms with no project <name>, and the few duplicates that crept in.
The top-level <properties> block had four keys defined twice. Maven keeps the last definition, so behavior was already determined; this commit just removes the dead earlier entries to make the resolved versions explicit. - netty-tcnative.version: drop 2.0.74.Final, keep 2.0.75.Final - jedis.version: drop 7.3.0, keep 7.4.1 - netty.version: drop redundant duplicate (both were 4.2.12.Final) - activemq.version: drop redundant duplicate (both were 6.2.4)
reiabreu
approved these changes
Apr 28, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The storm-multilang/, storm-dist/, external/ and examples/ trees previously listed their children directly in the root pom (or its profiles) without an aggregator pom of their own, which broke the standard Maven multi-module shape (no
mvn -pl <group> -ambuilds, no shared parent for grouped concerns) and made the root module list noisy. Pom display names were also inconsistent or missing across the tree.