Re: Lucene 9.0 snapshot names

> On a different note, does gradle use the same configuration for when we do > actual releases? I’m still confused as to why it wanted my GPG password in > plaintext in a file somewhere. > I don't think we've done a proper release with gradle workflow. I can't remember doing much in that area -

Re: Lucene 9.0 snapshot names

> On 25 May 2021, at 11:24, Dawid Weiss > wrote: > > > Ok. In that case we can make it simpler by not adding the signing plugin to > that (local) maven publication? Unless it makes sense to have it. Let me > know, this is a trivial change. +1, that would be

Re: Lucene 9.0 snapshot names

Ok. In that case we can make it simpler by not adding the signing plugin to that (local) maven publication? Unless it makes sense to have it. Let me know, this is a trivial change. D. On Tue, May 25, 2021 at 8:36 AM Uwe Schindler wrote: > Maven consumers only needs checksums to work correctly.

Re: Lucene 9.0 snapshot names

Maven consumers only needs checksums to work correctly. The signatures are optional. Uwe Am May 25, 2021 6:16:08 AM UTC schrieb Dawid Weiss : >These signatures are what makes a Maven repository a Maven repository >though. Even when you "deploy" to a local folder, it preserves the >files

Re: Lucene 9.0 snapshot names

These signatures are what makes a Maven repository a Maven repository though. Even when you "deploy" to a local folder, it preserves the files required for other Maven-toolchain tools. I'm not sure how it behaves without signatures. It is entirely doable to create a non-maven-task based assembly

Re: Lucene 9.0 snapshot names

Sounds like this would be a good addition to /dev-docs/... ~ David Smiley Apache Lucene/Solr Search Developer http://www.linkedin.com/in/davidwsmiley On Mon, May 24, 2021 at 12:56 PM Uwe Schindler wrote: > Thank for this tipp! Helps for Solr, too. I was giving up because it > always wanted to

Re: Lucene 9.0 snapshot names

Thank for this tipp! Helps for Solr, too. I was giving up because it always wanted to sign, that Jenkins can't easily do. Uwe Am May 24, 2021 8:03:51 AM UTC schrieb Alan Woodward : >Passing -x signJarsPublication skipped the signing step so I’m good to >go. Thanks everyone for the help! > >>

Re: Lucene 9.0 snapshot names

Passing -x signJarsPublication skipped the signing step so I’m good to go. Thanks everyone for the help! > On 23 May 2021, at 21:11, Dawid Weiss wrote: > > > Create a temporary pgp key for use with signing and use it to sign your maven > artifacts? I don't know if there is a way to use an

Re: Lucene 9.0 snapshot names

Create a temporary pgp key for use with signing and use it to sign your maven artifacts? I don't know if there is a way to use an agent - perhaps there is. Hoss did some work with manual artifact signing recently (and this used the agent). I never had the need for this. Dawid On Sat, May 22,

Re: Lucene 9.0 snapshot names

Passing -Dversion.suffix does indeed work, thanks Uwe! The next Yak to shave is that gradle is now complaining that it can’t sign the artefacts. From my reading it seems that I have to set things up in my gradle.properties file, including my password in plain text. This seems … wrong? I

Re: Lucene 9.0 snapshot names

The default suffix in this system prop is "SNAPSHOT" and the timestamp comes then from Maven's internal Logic, this cannot be changed. By overriding the suffix explicit (as said before and find by Jenkins) you convert it to an official "release" in Maven's sense and it is no longer a snapshot.

Re: Lucene 9.0 snapshot names

Jenkins does this already: https://ci-builds.apache.org/job/Lucene/job/Lucene-Artifacts-main/242/ It uses build number! The system property "version suffix" is responsible and is set by Jenkins. See in command line: [Lucene-Artifacts-main] $

Re: Lucene 9.0 snapshot names

In principal it makes sense, but is there any chance the build artifact could vary for the same SHA? We hope not, I think, but stranger things have happened. Probably an edge case not worth worrying about though, and relying on the build server's clock doesn't seem great, so +1 from me, although I

Lucene 9.0 snapshot names

Hi all, I’m preparing a local lucene 9.0 snapshot build and I notice that the jar files generated by `./gradlew mavenToLocalFolder` are called something like `lucene-suggest-9.0.0-20210520.111833-1-javadoc.jar` - in other words, they are including a timestamp. For my setup I’d like to replace