You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Sometimes the default settings of OFT don't fit your project.
Describe the solution you'd like
To allow overriding the standard settings of OFT per project we will introduce a project central configuration file that takes precedence over the built-in configuration of OFT. Command line options always win.
Describe alternatives you've considered
Specifying command line options for every call is inconvenient. We also considered external property files but these also require at least one command line options.
Additional context
For an example why this is useful please check #352.
The only place where auto-detection does not work at the moment are legacy short tags. Those are deprecated and scheduled for removal in OFT 5 late 2027.
Everything that needs configuration can be configured via command line or API. I am closing this issue.
Usage of config files is a popular convention across tools. Linters, compilers, code editors, and so on.
When I have a config file in a project this is easier for collaboration. If in project we ignore some artifact types or specification statuses, we can write one config file .oft and then anybody who runs oft will apply this configuration in our project. No need to share the exact CLI command.
There could be several tools working with OFT. OFT CLI, LSP server, build tool (gradle plugin) - one config file will already govern all of these tools.
Activity
redcatbear commentedon Feb 11, 2024
I suggest using Java properties for this purpose. It's a simple and non-invasive solution.
InAnYan commentedon Aug 14, 2026
Also useful if several tools are used in a project, e.g. Java project with gradle plugin (1 tool) and LSP server (second tool)
redcatbear commentedon Aug 22, 2026
The only place where auto-detection does not work at the moment are legacy short tags. Those are deprecated and scheduled for removal in OFT 5 late 2027.
Everything that needs configuration can be configured via command line or API. I am closing this issue.
InAnYan commentedon Sep 2, 2026
I don't agree with closing the issue:
.oftand then anybody who runs oft will apply this configuration in our project. No need to share the exact CLI command.