On Mon, Nov 10, 2025, 18:27 Gary Gregory <[email protected]> wrote:
> On Mon, Nov 10, 2025 at 4:44 PM Emmanuel Bourg <[email protected]> wrote: > > > > On 10/11/2025 18:55, Gary Gregory wrote: > > > > > I think it needs to run before any tests or anything time consuming is > > > done. It's so lame when a build runs and it only fails at the very end > > > because something as simple as a messed up or missing license header. > > > > > > Can you make it do that? > > > > Binding the plugin to the process-test-resources phase would do that I > > guess. > > > > But the issue here is a question of balance between one or two devs > > having to relaunch the tests once due to a bad file vs everyone paying > > the cost of the full project verification on every build. > > > > For commons-cli for example, rat spends 21 seconds checking the files on > > my laptop (ok it's 8 years old but that's 45% of the time spend for 'mvn > > compile'). > If you really think it's worth making the change, then ok. Gary > Yeah, my FOSS machine was about that age when I replaced it with a new > one a year ago. For CLI, 'mvn clean compile' takes 2.3 seconds here. I > bet a lot of that time is waiting for console IO, since most Maven > plugins are beyond verbose by default. > > Gary > > > > > Emmanuel Bourg > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [email protected] > > For additional commands, e-mail: [email protected] > > >
