apache / apache/maven-invoker-plugin

[MINVOKER-293] Profiles are passed to invoked executions

Open
#519 1 comment 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
22
Forks
35
Avg merge
2d 17h
Merged PRs (30d)
7

Description

**[Zbigniew Lis](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=zbilis)** opened **[MINVOKER-293](https://issues.apache.org/jira/browse/MINVOKER-293?redirect=false)** and commented

If you run "mvn generate-resources -PmyProfile" on a project that **uses** maven-invoker-plugin, then myProfile is passed to whatever execution you have configured in this plugin **in addition** to what is configured in plugin configuration, or in invoker.properties file.

To reproduce it using attached project: if you run "mvn generate-resources -PmyProfile" on "maven-invoker-profile-inheritance" project, then you'll see that the profile is being activated in the "maven-invoker-profile-inheritance-dependency" project (and in result the echo-maven-plugin will be executed) I couldn't find a way to prevent this behavior.

---

**Affects:** 3.0.1, 3.2.2

**Attachments:**
- [maven-invoker-profile-inheritance.zip](https://issues.apache.org/jira/secure/attachment/13035213/maven-invoker-profile-inheritance.zip) (_6.03 kB_)

Contributor guide

No contributing guide indexed for this repository

Research direction

Unpack the attached maven-invoker-profile-inheritance project and run `mvn generate-resources -PmyProfile` as described. Inspect the maven-invoker-plugin configuration and any invoker.properties involved in the invoked dependency project. Done means the caller's myProfile is not propagated to the invoked execution unless explicitly configured there.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
build-system
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.