Thanks Andrea, some good news - because of how the header regex was setup
there was no need to use property expansion to select a different set of
rules.
As the QA check is not really desired in a standalone project I have
isolated it into a profile (could not see any way to reduce duplication).
To get a clean standalone pom.xml for examples I ended up using sphinx very
carefully in the docs:
.. literalinclude:: /../../tutorials/quickstart/pom.xml
:language: xml
:end-before: <profiles>
:append: </project>
It has now been five days, and I would like to ask for any further input,
or this PR to be merged.
Yes this is quick, our proposal procedure is:
- svn access for changes is granted within 3 days from the proposal
>
- proposal is accepted ‘automatically’ within 15 days (unless objections
> are raised)
>
--
Jody Garnett
On Mar 21, 2022 at 1:43:58 AM, Andrea Aime <
andrea.a...@geosolutionsgroup.com> wrote:
> Hi Jody,
> I did not know the answer, so I did a quick research. It seems one can
> configure property expansion
> in the checkstyle configuration file, that would allow to switch expected
> header on a per module basis:
>
>
> https://maven.apache.org/plugins/maven-checkstyle-plugin/examples/custom-property-expansion.html#:~:text=Checkstyle%20uses%20the%20property%20expansion,the%20checks%20performed%20by%20Checkstyle
> .
>
> Cheers
> Andrea
>
> On Mon, Mar 21, 2022 at 3:39 AM Jody Garnett <jody.garn...@gmail.com>
> wrote:
>
>> Thanks Ian,
>>
>> I actually have a technical question for Andrea on this one, one of the
>> tasks is "Check if docs can skip QA check for LGPL headers". Any tips on
>> how to set that up, or override the configuration to check for CC0 headers?
>> --
>> Jody Garnett
>>
>>
>> On Mar 19, 2022 at 2:20:08 AM, Ian Turton <ijtur...@gmail.com> wrote:
>>
>>> +1
>>>
>>> Ian
>>>
>>> On Fri, 18 Mar 2022 at 20:59, Jody Garnett <jody.garn...@gmail.com>
>>> wrote:
>>>
>>>> Here is proposal
>>>> https://github.com/geotools/geotools/wiki/Change-tutorial-and-example-code-from-public-domain-to-CC0
>>>> --
>>>> Jody Garnett
>>>>
>>>>
>>>> On Fri, 18 Mar 2022 at 13:48, Jody Garnett <jody.garn...@gmail.com>
>>>> wrote:
>>>>
>>>>> I would like to do a quick proposal:
>>>>>
>>>>> > Use CC0 for our documentation and source code examples, in keeping
>>>>> with our public domain policy in the developers guide
>>>>>
>>>>> CC0 is as I understand it a more useful way to release copyright,
>>>>> while public domain can be american centric.
>>>>>
>>>>> Context - tripped over a couple of things looking at tutorial code:
>>>>> - Sample code was changed to LGPL at some point, when the project
>>>>> policy is public domain
>>>>> - Some of the pom.xml and pom2.xml examples no longer match since
>>>>> these projects are not tested except by hand. I have learned a bit about
>>>>> maven and we can set these up as distinct standalone projects (using
>>>>> deploy.skip) to avoid publishing.
>>>>>
>>>>> There is a pull request here
>>>>> https://github.com/geotools/geotools/pull/3823 showing the result
>>>>> (including developers guide change).
>>>>> --
>>>>> Jody Garnett
>>>>>
>>>> _______________________________________________
>>>> GeoTools-Devel mailing list
>>>> GeoTools-Devel@lists.sourceforge.net
>>>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>>>
>>>
>>>
>>> --
>>> Ian Turton
>>>
>> _______________________________________________
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>
>
> --
>
> Regards,
>
> Andrea Aime
>
> ==
> GeoServer Professional Services from the experts!
>
> Visit http://bit.ly/gs-services-us for more information.
> ==
>
> Ing. Andrea Aime
> @geowolf
> Technical Lead
>
> GeoSolutions Group
> phone: +39 0584 962313
>
> fax: +39 0584 1660272
>
> mob: +39 333 8128928
>
> https://www.geosolutionsgroup.com/
>
> http://twitter.com/geosolutions_it
>
> -------------------------------------------------------
>
> Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE
> 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si
> precisa che ogni circostanza inerente alla presente email (il suo
> contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è
> riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il
> messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra
> operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
>
> This email is intended only for the person or entity to which it is
> addressed and may contain information that is privileged, confidential or
> otherwise protected from disclosure. We remind that - as provided by
> European Regulation 2016/679 “GDPR” - copying, dissemination or use of this
> e-mail or the information herein by anyone other than the intended
> recipient is prohibited. If you have received this email by mistake, please
> notify us immediately by telephone or e-mail
>
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
