How to control which Maven executable and settings file Frogbot uses for the internal dep-tree build?
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
When Frogbot builds the Maven dependency tree, it runs ./mvnw directly:
failed running command './mvnw org.apache.maven.plugins:maven-install-plugin:3.1.1:install-file
-Dfile=/tmp/jfrog.cli.temp.-xxx/maven-dep-tree.jar -B': exit status 1
This fails in our air-gapped environment, not sure why exactly. But it does not seem to use my wrapper or my settings for maven in my repo .mvn/
Question: Is there any supported way, environment variable, config option, or otherwise, to control the Maven executable or pass additional arguments specifically to the internal dep-tree build step?
Frogbot version: 2.32.0
CI: GitLab
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing Frogbot's internal Maven dependency-tree build entry point and how it invokes ./mvnw in version 2.32.0. Check the available configuration and environment-variable handling, then verify the result in GitLab CI with the air-gapped setup. Done means the Maven executable and settings or additional arguments can be controlled for this build step, or the limitation is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, java
- Domain
- build-system, ci-cd, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100