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
bragern
changed the title
Bug: .jqassistant.yml of a maven module not or only partially applied
.jqassistant.yml of a maven module not or only partially applied
Nov 14, 2023
The implementation has been extended such that .jQAssistant.yml files are evaluated from the reactor execution root as well as from the current module. This allows for project-wide configs as well as module specific configs, e.g. additional includes for the scanner. Note that some settings (e.g. store) are always applied globally.
See example in my github: https://github.com/bragern/jqa-groups-test/tree/main/jqa-groups-test
(sorry, already had it written in my format but it translates well to yours)
Two Issues observed there
1) Not recognizing groups configured in '.jqassistant.yml' of a maven module when building parent
steps to recreate
observed
On 'jqa-groups-test-module/' analysis happens in 'jqassistant-maven-plugin:2.0.8:analyze':
On 'jqa-groups-test/' nothing happens in 'jqassistant-maven-plugin:2.0.8:analyze':
expected
No matter if the build is started from parent or module, the configured group in '.jqassistant.yml' of the
module should be used for jqa analysis.
As you can see in issue 2) the '.jqassistant.yml' is definitely used in both cases but the configured groups
seem to be ignored.
2) Not recognizing '.jqassistant.yml' of a maven module at all when building parent
steps to recreate
observed
I also observed other parameters not to be used from the yml so it seems the entire yml is not loaded at all.
expected
No matter if the build is started from parent or module, the '.jqassistant.yml' of the module should be used
during module build
The text was updated successfully, but these errors were encountered: