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
That's because the two Property providers in com.mycila.maven.plugin.license.git use seperate JGit rev walks for (nearly) every property their provide, and all properties are eagerly provided.
For projects not using all provided properties to build header text this will result in unnecessary rev walks.
Any alternative you've considered ?
No.
The text was updated successfully, but these errors were encountered:
Playing with lazy evaluation of provided git properties, see frawa#1, now #877
On a project using only using license.git.copyrightLastYear and <license.git.maxCommitsLookup>1 I observe speedup for licence:check by a factor 3, from 15s down to 5s.
On a bigger project the speedup was 4, from 2min to 3s.
I wonder if that approach is worth being continued?
frawa
linked a pull request
Jan 8, 2025
that will
close
this issue
Describe the feature
Using header properties provided from git, like
license.git.copyrightLastYear
, can be slow,even used together with
That's because the two Property providers in
com.mycila.maven.plugin.license.git
use seperate JGit rev walks for (nearly) every property their provide, and all properties are eagerly provided.For projects not using all provided properties to build header text this will result in unnecessary rev walks.
Any alternative you've considered ?
No.
The text was updated successfully, but these errors were encountered: