Thanks a lot, I opened an issue and will start the vote. https://github.com/apache/incubator-baremaps/issues/907
Best, Bertil > On 14 Dec 2024, at 17:59, Julian Hyde <jhyde.apa...@gmail.com> wrote: > > I have never paid much attention to those fields. I don’t think that they > affect licensing, and therefore it’s not urgent to fix them before the > release. I would log a case and fix it for next release. > > Julian > >> On Dec 14, 2024, at 03:35, Bertil Chapuis <bchap...@gmail.com> wrote: >> >> Thanks a lot for checking the artifacts. >> >> Before starting the vote, I decided to verify everything again and noticed >> that the autogenerated META-INF/MANIFEST.MF file contains the following >> information. >> >> Manifest-Version: 1.0 >> Created-By: Maven JAR Plugin 3.3.0 >> Build-Jdk-Spec: 21 >> Specification-Title: baremaps-csv >> Specification-Version: 0.8 >> Specification-Vendor: baremaps >> Implementation-Title: baremaps-csv >> Implementation-Version: 0.8.1 >> Implementation-Vendor: baremaps >> Build-Date: 2024-11-09T13:13:45Z >> Build-Jdk: 21.0.4 >> Build-Version: 0.8.1 >> >> Is the vendor field ok with baremaps or could this compromise the vote on >> the incubator mailing list? I’d prefer to have the same commit for the >> source release and the artifacts, but I can also try to fix this after the >> release of rc4. Here is my proposition for the future manifest files, it >> will probably require to update all the pom.xml files: >> >> Manifest-Version: 1.0 >> Created-By: Maven JAR Plugin 3.3.0 >> Build-Jdk-Spec: 21 >> Specification-Title: baremaps-csv >> Specification-Version: 0.8 >> Specification-Vendor: The Apache Software Foundation >> Implementation-Title: baremaps-csv >> Implementation-Version: 0.8.1 >> Implementation-Vendor: The Apache Software Foundation >> Build-Date: 2024-11-09T13:13:45Z >> Build-Jdk: 21.0.4 >> Build-Version: 0.8.1 >> >> Best, >> >> Bertil >> >> >>> On 12 Dec 2024, at 03:45, Julian Hyde <jhyde.apa...@gmail.com> wrote: >>> >>> The maven artifacts look OK. The directory structure contains a directory >>> for each module, and each module has .jar, .-javadoc.jar, -sources.jar >>> files and appropriate hashes. >>> >>> Julian >>> >>> >>>>> On Dec 8, 2024, at 12:02 PM, Bertil Chapuis <bchap...@gmail.com> wrote: >>>> >>>> Hello Everyone, >>>> >>>> The release artifacts are now available on Nexus. Apparently, they have >>>> passed the automated checks performed by the server, but I assume there >>>> are other factors to consider. Also, a vote seems required to release >>>> them. Could someone experienced with this process have a look at them and >>>> provide a preliminary feedback before launching the vote (Martin, I guess >>>> that you may have done the same for Apache SIS at some point)? My main >>>> task when preparing the JAR files consisted in replacing the default >>>> LICENSE and NOTICE files with the ones located at the root of the baremaps >>>> repository [2]. >>>> >>>> [1] >>>> https://repository.apache.org/content/repositories/orgapachebaremaps-1008/ >>>> [2] https://infra.apache.org/publishing-maven-artifacts.html >>>> >>>> Thank you for your help and best regards, >>>> >>>> Bertil >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >>>> For additional commands, e-mail: dev-h...@baremaps.apache.org >>>> >>> >>> >>> --------------------------------------------------------------------- >>> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >>> For additional commands, e-mail: dev-h...@baremaps.apache.org >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org >> For additional commands, e-mail: dev-h...@baremaps.apache.org >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@baremaps.apache.org > For additional commands, e-mail: dev-h...@baremaps.apache.org >
