Fwd: License headers inside Javadoc comments

2024-01-26 Thread James Turton
Just a forward to complete the records. Forwarded Message Subject:Re: License headers inside Javadoc comments Date: Fri, 26 Jan 2024 15:38:29 +0200 From: James Turton To: P. Ottlinger , d...@creadur.apache.org CC: dev Thanks Phil. Here's some

Re: License headers inside Javadoc comments

2024-01-26 Thread James Turton
Thanks Paul I don't know how to configure the license plugin. But, I do suspect a Python file (or shell script) could make a one-time pass over the files to standardize headers into whatever format the team chooses. Only the first line of each file would change. I put more information in my

Re: License headers inside Javadoc comments

2024-01-26 Thread James Turton
Thanks Phil. Here's some background [1] which comes from before I was involved with Drill. What they wanted was for the license header checker to accept, in .java files, /* * Licensed to the Apache Software Foundation (ASF) under one * or more contributor license agreements. See the

Re: License headers inside Javadoc comments

2024-01-26 Thread P. Ottlinger
Hi James, thanks for reaching out! Am 26.01.24 um 08:21 schrieb James Turton: I'd like to ask about a feature to prevent RAT from allowing license headers to appear inside Javadoc comments  (/**) while still requiring them in Java comments (/*) in .java files. Currently the Drill project

Re: License headers inside Javadoc comments

2024-01-26 Thread Paul Rogers
Hi James, For some reason, Drill started with the license headers in Javadoc comments. The (weak) explanation I got was that we never generate Javadoc, so it didn't really matter. Later, we started converting the headers to regular comments when convenient. If we were to generate Javadoc, having