There is documentation for how to rewrite the matchers for the new matcher framework. As you probably recall it was added after the 0.16.0 fiasco. We may need to make that more visible.
I would like to try to get some code into 17 that reads the SPDX license templates and matches against the information there. This will give us a way to add many more reviewed license definitions and should be fairly easy given that there is an SPDX tool library in Java with ASF2.0 licenses. I think I heard about a plugin library for Maven 3.x that allows for properties of nodes in the pom.xml, I also heard that this was tobe in 4.x but I have not seen anything concrete about that. At this point, I am not going to remove the back ported stuff, unless it starts to conflict with what we need to do to move the UI forward. I do think it should be removed in 0.17 or 0.18. Claude On Mon, Mar 18, 2024 at 9:24 PM P. Ottlinger <[email protected]> wrote: > Hi Claude, > > thanks for raising the issue .... > > Am 18.03.24 um 14:03 schrieb Claude Warren: > > We deprecated some things after 0.15 and put them back in 0.16.1 to make > > the migration easier. Should we remove them in 0.17. This has an impact > > on the solution to RAT-364 as well as the complexity of the code base. > > Personally I wouldn't mind removing the deprecated stuff if a proper > documentation is provided and thus a migration path is easy to follow > for upstream users. > > https://issues.apache.org/jira/browse/RAT-364 > > > Also should we move to supporting Maven 4.x in 0.17 or do we need a > > solution that can support both maven 3 and 4? > > As Maven4 is still in alpha, I'd assume we need a solution that works > out with mvn3 and mvn4 .... > > Just my 2ct, > > Phil > -- LinkedIn: http://www.linkedin.com/in/claudewarren
