Add a property to specify the tool version by repo
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 372
- Forks
- 107
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 5
Description
Is your feature request related to a problem? Please describe.
When scanning multiple java project, we need to specify for each app the java version used for the compilation.
Describe the solution you'd like to see
A param in the frogbot config to specify the tool version to use for an app (java 11-17/ node 18 etc...)
Or a param to set an environment variable for an app so we can set JAVA_HOME
Describe alternatives you've considered
Multiple frogbot pipelines for each Java versions
Additional context
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
No files, tests, or configuration entry points are identified in the issue. Start by locating frogbot's configuration handling and the code that scans multiple applications, then determine how per-application Java or Node.js versions would be represented. Done means the configuration supports distinct tool versions or environment settings per application and the behavior is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, node.js
- Domain
- security, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100