mojohaus/license-maven-plugin

Aggregate third party report fails on multimodule maven that has module with cross dependencies

Open

#317 opened on Apr 3, 2019

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Java (127 forks)auto 404
add-third-partyhelp wanted

Repository metrics

Stars
 (115 stars)
PR merge metrics
 (PR metrics pending)

Description

We are performing a release mvn release:prepare release:perform on a multimodule maven project. Some module depends from other modules. The typical scenario is: parent |->model |->client (depends from model) |->web (depends from model)

The release plugin change the version and run a clean verify in all pom.xml after that run deploy site:deploy goals. The aggregate-add-third-party mojo run on parent project and to resolve all dependencies of children modules. It fails when one of child module depends on other child (web -> model) because aggregate-add-third-party is not able to resolve the child module with the new version since it has been never installed.

Contributor guide

Research direction
Investigate the Maven reactor resolution order and how the aggregate add third party mojo resolves child module dependencies. Consider installing modules locally before running site:deploy or adjusting the plugin to resolve from reactor instead of local repository.
Tech stack
java
Domain
build systemdeveloper experience
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
MavenJava
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65