Hi, Guess you need to exclude all release*.md, most *.xml and *.properties (legacy *must* not be fixed since it would break). A codemod could fix all the other issues (code) but would also break all consumers so as for the past renaming I'm really -1 on such rework which do not solve the community issue it tries to solve (actually it makes it more complex when the term is kind of used for years).
So in terms of actions I think the clc could use a clc.properties or clc.json in the repository (please no yaml) to exclude all false positive warnings which would lead to almost nothing in karaf (it is the same on other repos I reviewed, mainly noise warnings). Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <https://rmannibucau.metawerx.net/> | Old Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book <https://www.packtpub.com/application-development/java-ee-8-high-performance> Le lun. 30 août 2021 à 09:43, Francois Papon <francois.pa...@openobject.fr> a écrit : > Hi, > > I checked the result of the Karaf repo analysis and I don't know how we > could fix the thousand of issues... > > https://clc.diversity.apache.org/analysis.html?project=karaf.git > > The most are related to the blacklist feature so It will be a huge > effort and a migration step for users. > > Thoughts? > > regards, > > -- > François > fpa...@apache.org > >
