Re: Minutes: JDO TCK Conference Call Thursday May 19 11 PM PDT 20 CEST

2022-05-20 Thread Bouschen, Michael
Hi, I agree renaming is the best option. I tried it and it seems to work. * Renamed LICENSE.txt to LICENSE and NOTICE.txt to NOTICE. * I also changed the NOTICE file to include the correct year 2022. * For the api artifacts the two files LICENSE and NOTICE are generated by the

[jira] [Assigned] (JDO-813) Avoid duplicated license and notice files in distribution artifact

2022-05-20 Thread Michael Bouschen (Jira)
[ https://issues.apache.org/jira/browse/JDO-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen reassigned JDO-813: Assignee: Michael Bouschen > Avoid duplicated license and notice files in distribution

[jira] [Updated] (JDO-813) Avoid duplicated license and notice files in distribution artifact

2022-05-20 Thread Michael Bouschen (Jira)
[ https://issues.apache.org/jira/browse/JDO-813?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Bouschen updated JDO-813: - Fix Version/s: JDO 3.2.1 > Avoid duplicated license and notice files in distribution artifact >

[jira] [Created] (JDO-813) Avoid duplicated license and notice files in distribution artifact

2022-05-20 Thread Michael Bouschen (Jira)
Michael Bouschen created JDO-813: Summary: Avoid duplicated license and notice files in distribution artifact Key: JDO-813 URL: https://issues.apache.org/jira/browse/JDO-813 Project: JDO

Re: Minutes: JDO TCK Conference Call Thursday May 19 11 PM PDT 20 CEST

2022-05-20 Thread Craig Russell
Yes. If there is a LICENSE and NOTICE in the root, and the plugin does not overwrite them, I think we are good renaming our xxx.txt to xxx and be done with it. Craig > On May 20, 2022, at 5:03 AM, TIlmann wrote: > > I looked at some other repositories, they appear to have LICENSE and >

Re: Minutes: JDO TCK Conference Call Thursday May 19 11 PM PDT 20 CEST

2022-05-20 Thread TIlmann
I looked at some other repositories, they appear to have LICENSE and NOTICE in their repository root. https://github.com/apache/spark https://github.com/apache/derby https://github.com/apache/kafka Didn't you mention something like that the plugin may not overwrite files that already exist?

Re: Minutes: JDO TCK Conference Call Thursday May 19 11 PM PDT 20 CEST

2022-05-20 Thread Bouschen, Michael
Hi Tilmann, no, the files LICENCE and NOTICE are generated by 'mvn install'. So if we need a LICENSE file in the source repository, we haven an issue here. Regards Michael > So I propose to remove the files LICENSE.txt and NOTICE.txt and use the files as generated by the

Re: Minutes: JDO TCK Conference Call Thursday May 19 11 PM PDT 20 CEST

2022-05-20 Thread TIlmann
>  So I propose to remove the files LICENSE.txt and NOTICE.txt and use the files as generated by the maven-remote-resources-plugin Just for my understanding, we would still have LICENSE/NOTICE files in the repository, right? I think at least the LICENSE(.txt) file is pretty much mandatory in the