apache / apache/maven-archetype

[ARCHETYPE-549] When running archetype post-phase plugin is ignoring settings file location proved in command line (-s)

Open
#542 0 comments 0 reactions 0 assignees View on GitHub
bug priority:major
Dominant language
Java
Stars
148
Forks
181
Avg merge
1d 20h
Merged PRs (30d)
8

Description

**[Ognjen Milic](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=ognjenmi)** opened **[ARCHETYPE-549](https://issues.apache.org/jira/browse/ARCHETYPE-549?redirect=false)** and commented

We are providing settings file to Maven with -s command line parameter. This works fine everywhere except for archetype plugin in create-from-project goal.

Plugin works fine until it comes to archetype post-phase where it obviously runs Maven again but without passing -s command line parameter and therefore ignores settings file location.

This breaks our build as we are using repository manager specified in settings file and central Maven repository is not visible for the build server directly. Therefore plugin can't download its dependencies and/or update timestamp.

We can not use default settings file location on the build server as other teams use it with different settings and this is not allowed and there is no way to work in that way as a workaround.

 

 

---

**Affects:** 3.0.1

1 votes, 2 watchers

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by tracing the create-from-project goal through its archetype post-phase, focusing on where it invokes Maven again. Reproduce the build with a non-default settings file passed through -s and verify that the post-phase uses that location and can resolve dependencies through the configured repository manager.

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.