Feature to not deploy parent module of a multi-module project.

Open
#622 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
java
Domain
build-system

Research direction

No files, tests, or entry points are named. Start by examining how deployment handles multi-module Maven projects and review the related GitHub Community discussion. Done means a parent module without a JAR can be skipped while its child modules still deploy successfully.

Written by the indexing model from the issue text.

Description

enhancement
New feature, improvement proposal

We have a multi-module project where the parent module has no actual content, and references child modules to be built. When we use mvn deploy to the Github Maven repository, Github refuses the upload of the parent module because there is no jar to upload. This causes all the child modules to not deploy either, since the parent module failed. Is there a way to avoid deploying the parent module?

Related: https://github.com/orgs/community/discussions/44788

Dominant language
Java
Stars
78
Forks
76
Avg merge
2d 5h
Merged PRs (30d)
13

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/maven-deploy-plugin

All issues in apache/maven-deploy-plugin

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.