https://docs.gradle.org/current/userguide/publishing_maven.html#publishing_maven
I know absolutely _nothing_ about it, just that it exists…. > On Jun 15, 2020, at 4:07 PM, Mike Drob <[email protected]> wrote: > > David - Does the Gradle build offer something easier to maintain than a very > old Ant Maven plugin? > > On Mon, Jun 15, 2020 at 8:43 AM Ishan Chattopadhyaya > <[email protected]> wrote: > Hi David, > It may be unrelated, but I was similarly puzzled when all hardcoded Maven > URLs had https://, but it was still resolving against http:// and failing. > Here's how I tackled it: > https://issues.apache.org/jira/browse/LUCENE-9170 > Regards, > Ishan > > On Mon, Jun 15, 2020 at 11:59 AM David Smiley <[email protected]> > wrote: > No; it's another option for people who would rather use Maven instead of Ant. > Where I work I've found it useful because it allows you to fork Solr and > push the artifacts (plus source & docs) to a company Maven repo. It wasn't > apparent to me how to do that in the Ant build. Also, it's substantially > easier to understand than the Ant build IMO. > > I looked at the failures and it's because of Maven central being HTTPS only > now yet the build is trying HTTP. I am locally playing with this to fix > it... common-build.xml line 718 is using an old Ant Maven plugin thing that > probably has a built-in hardcoded notion of where Maven central is. I added > the repo explicitly with HTTPS and I got the build to progress but now am > stuck trying to resolve a "protobuf-bom" dependency wherein it's still using > the old HTTP URL for some inexplicable reason. This dependency is of scope > "import" which I've never seen before. Shrug. I'll look at this more later. > > ~ David > > > On Sun, Jun 14, 2020 at 10:58 PM Michael Sokolov <[email protected]> wrote: > I'm not sure what the purpose of these builds is? Is it to push artifacts to > Maven central? > > On Sun, Jun 14, 2020, 10:09 PM Mike Drob <[email protected]> wrote: > Devs, > > I was looking at the maven builds and they have been failing for a long time. > For example > https://builds.apache.org/view/L/view/Lucene/job/Lucene-Solr-Maven-master/ > > The question is, are these worth fixing, with the eventual move to Gradle? If > not, can we disable the jobs? > > Mike --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
