[STORM-3942] mvn package in storm-dist relies on files being available in sibling directories

Description

Contributor guide

Tech stack

java

Domain

build system

Issue type

bug

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

half day

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

basic Maven knowledge

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

40

Research direction

Examine the pom.xml files in storm dist/binary and storm dist/source directories. Identify the dependencies on sibling directories (e.g., storm webapp) that may not be built yet. Investigate using maven enforcer plugin to validate the existence of required files before packaging, as suggested in the issue. Look at the Maven Enforcer plugin documentation to define rules that check for missing files and fail the build with a clear error message.