Network glitches in snapshot publishing. I've filed this one:
https://github.com/apache/lucene/issues/14663
D.
On Wed, May 14, 2025 at 7:02 AM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Sn
Added a sticky tag to run on lucene-solr-1 for now.
On Wed, Apr 30, 2025 at 12:09 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Snapshots-10.x/181/
>
> No tests ran.
>
> Build Log:
, 2025 at 4:41 AM Apache Jenkins Server
wrote:
>
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Snapshots-main/2161/
>
> No tests ran.
>
> Build Log:
> [...truncated 77 lines...]
> BUILD FAILED in 59s
> 22 actionable tasks: 22 executed
>
>
I've modified the configuration to use Java 23.
D.
On Thu, Feb 27, 2025 at 12:41 PM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:
> Build:
> https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Snapshots-main/2098/
>
> No tests ran.
>
> Build
> I think, if smoke tester knows the version, it could just check the staging
> repo, too. It is just another URL!?
Yes, it's an URL.
> If the staging repository on nexus has a hash inside (I think they have),
> maybe the release wizard places some file with the URL of the actual staging
> rep
17.11.2022 um 14:37 schrieb Adrien Grand:
I remember another proposal which consisted of using the Gradle build
to rebuild Maven artifacts at the type of uploading to Nexus, which I
liked less because it involved re-building, and who knows what may
happen that could produce slightly different
> I remember another proposal which consisted of using the Gradle build to
> rebuild Maven artifacts at the type of uploading to Nexus, which I liked
> less because it involved re-building, and who knows what may happen that
> could produce slightly different binaries. I like your
I remember another proposal which consisted of using the Gradle build to
rebuild Maven artifacts at the type of uploading to Nexus, which I liked
less because it involved re-building, and who knows what may happen that
could produce slightly different binaries. I like your new proposal better
Yeah, I thought so. I'd love to help improve this as part of the next
release - it should really be simple. I know the old way was to have maven
artifacts separately (to agree/vote upon) but in my opinion it wouldn't
change much if the release manager pointed to release artifacts + mave
I remember using a 8.x build to do that for the 9.0 release.
On Thu, Nov 17, 2022 at 1:54 PM Dawid Weiss wrote:
>
> I looked at an old issue related to maven artifact publishing and I
> noticed the release wizard still gives instructions to use the ant-based
> script (which isn
I looked at an old issue related to maven artifact publishing and I noticed
the release wizard still gives instructions to use the ant-based script
(which isn't there anymore?):
ant clean stage-maven-artifacts
I'm sorry to ask but how did release managers stage maven artifacts so
I fixed this.
Uwe
Am 14. Mai 2022 19:47:25 UTC schrieb Apache Jenkins Server
:
>Build:
>https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Snapshots-main/1091/
>
>No tests ran.
>
>Build Log:
>[...truncated 66 lines...]
>BUILD FAILED in 28s
>8 actionable ta
> I ended up cheating a bit and using the 8.11 Ant build to upload the
> Maven artifacts to Nexus before I saw Dawid's message.
If ant can do it then it surely can be ported to gradle though -
perhaps worth exploring as well? If you create an issue I'll take a
look,
although I a
I ended up cheating a bit and using the 8.11 Ant build to upload the
Maven artifacts to Nexus before I saw Dawid's message.
The bundle idea looks like a promising path to use for upcoming
releases. Since we require logging into Nexus anyway for promotion, it
doesn't make things worse
iss wrote:
> > I believe maven/nexus natively allows publishing an RC to the staging
> repo and then manually promoting to a release. Apache infra has this dual
> set up for us already.
> > Would gradle be able to hook into that process?
>
> If it's the same as other o
> I believe maven/nexus natively allows publishing an RC to the staging repo
> and then manually promoting to a release. Apache infra has this dual set up
> for us already.
> Would gradle be able to hook into that process?
If it's the same as other open source Nexus insta
I believe maven/nexus natively allows publishing an RC to the staging repo
and then manually promoting to a release. Apache infra has this dual set up
for us already.
Would gradle be able to hook into that process?
On Mon, Dec 6, 2021 at 9:15 AM Dawid Weiss wrote:
> Hi Adrien,
>
>
nd wrote:
>
> Hello,
>
> The release wizard still suggests using Ant for Maven publication:
>
> cd ~/.lucene-releases/9.0.0/lucene
> ant clean stage-maven-artifacts \
>
> -Dmaven.dist.dir=~/.lucene-releases/9.0.0/RC4/dist/lucene-9.0.0-RC4-rev-0b18b3b
9488
So the wizard should probably run the gradle equivalent
./gradlew mavenToApacheReleases -Dversion.release=
-PasfNexusUsername= -PasfNexusPassword=
Jan
> 6. des. 2021 kl. 14:19 skrev Adrien Grand :
>
> Hello,
>
> The release wizard still suggests using Ant for Maven pu
Hello,
The release wizard still suggests using Ant for Maven publication:
cd ~/.lucene-releases/9.0.0/lucene
ant clean stage-maven-artifacts \
-Dmaven.dist.dir=~/.lucene-releases/9.0.0/RC4/dist/lucene-9.0.0-RC4-rev-0b18b3b965cedaf5eb129aa41243a44c83ca826d/lucene/maven
\
-Dm2
for the network calls?
>
> On Sun, Oct 31, 2021 at 4:03 AM Dawid Weiss wrote:
> >
> >
> > Some temporary glitch, it seems:
> >
> > Could not GET '
> https://repository.apache.org/content/repositories/snapshots/org/apache/lucene/lucene-analysi
rg/apache/lucene/lucene-analysis-smartcn/maven-metadata.xml'.
> > Read timed out
>
>
> On Sun, Oct 31, 2021 at 4:34 AM Apache Jenkins Server
> wrote:
>>
>> Build:
>> https://ci-builds.apache.org/job/Lucene/job/Lucene-Maven-Snapshots-main/791/
>>
>
Some temporary glitch, it seems:
Could not GET
'https://repository.apache.org/content/repositories/snapshots/org/apache/lucene/lucene-analysis-smartcn/maven-metadata.xml'.
> Read timed out
On Sun, Oct 31, 2021 at 4:34 AM Apache Jenkins Server <
jenk...@builds.apache.org&
t; >> Cheers,
> >> -Greg
> >>
> >>
> >> On Mon, Aug 23, 2021 at 9:37 AM Houston Putman
> wrote:
> >> >
> >> > Thanks for calling this out Mike.
> >> >
> >> > It's related to SOLR-15089. I'll get it sorted
>
>> > It's related to SOLR-15089. I'll get it sorted out, as well as some test
>> > flakiness that were introduced by that ticket.
>> >
>> > - Houston
>> >
>> > On Mon, Aug 23, 2021 at 6:56 AM Michael McCandless
>> > wrote:
&
>
> > It's related to SOLR-15089. I'll get it sorted out, as well as some test
> flakiness that were introduced by that ticket.
> >
> > - Houston
> >
> > On Mon, Aug 23, 2021 at 6:56 AM Michael McCandless <
> luc...@mikemccandless.com> wro
ll as some test
> flakiness that were introduced by that ticket.
>
> - Houston
>
> On Mon, Aug 23, 2021 at 6:56 AM Michael McCandless
> wrote:
>>
>> This is the actual error -- ring any bells?:
>>
>> /home/jenkins/jenkins-slave/workspace/Lucene/Lucene-S
@mikemccandless.com> wrote:
> This is the actual error -- ring any bells?:
>
> /home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Solr-Maven-8.x/lucene/common-build.xml:726:
> Could not resolve artifacts: Could not find artifact
> com.amazonaws:aws-java-sdk-bom:jar:1.12.42 i
This is the actual error -- ring any bells?:
/home/jenkins/jenkins-slave/workspace/Lucene/Lucene-Solr-Maven-8.x/lucene/common-build.xml:726:
Could not resolve artifacts: Could not find artifact
com.amazonaws:aws-java-sdk-bom:jar:1.12.42 in central
(https://repo1.maven.org/maven2/)
Mike
ere is a work-around for this particular "import" scope scenario... or we
>> migrate to the new Maven Artifact Resolver Ant Task. I'm not even certain
>> that the new tasks don't have this problem but it's likely given the age of
>> the old tasks and curr
gt; there is a work-around for this particular "import" scope scenario... or we
> migrate to the new Maven Artifact Resolver Ant Task. I'm not even certain
> that the new tasks don't have this problem but it's likely given the age of
> the old tasks and current-ness of
I'll leave it to you then; thanks. I don't really have anything. You
could try to dig into the source of the old tasks we are using to see if
there is a work-around for this particular "import" scope scenario... or we
migrate to the new Maven Artifact Resolver Ant Task.
Thanks David.
I’ve disabled the 8.5, 8.x, and main branch maven builds for now, there’s
no point in running into the same failure every day.
Please re enable them if you get a chance to figure this out, otherwise
I’ll have time to start looking next week as well.
Do you have a JIRA or WIP
I don't know about what Gradle offers other than observing what Erick
shares, but I like to think that we can get rid of not only the Ant build
but the Maven build too. If there are obstacles, I'd prefer to figure them
out rather than settle for the complexity (and thus maintenance co
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 wrote:
>
> David - Does the Gradle build offer something easier to maintain than a very
> o
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 <
ichattopadhy...@gmail.com> wrote:
> Hi David,
> It may be unrelated, but I was similarly puzzled when all hardcoded Maven
>
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 S
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
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 wrote:
> Devs,
>
> I was looking at the maven builds and they have been failing for a long
> time. For example
> https://builds.apache.org/vi
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
and to
>> discuss the removal of this dependency.
>>
>> Thanks!
>>
>>
>>
>>
>>
>> Joel Bernstein
>> http://joelsolr.blogspot.com/
>>
>>
>> On Fri, Dec 27, 2019 at 6:11 PM Uwe Schindler wrote:
>>
>>> Sorry,
>
et project and to
> discuss the removal of this dependency.
>
> Thanks!
>
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/
>
>
> On Fri, Dec 27, 2019 at 6:11 PM Uwe Schindler wrote:
>
>> Sorry,
>>
>>
>>
>> the Ivy build
issues.apache.org/jira/browse/LUCENE-8807 (Lucene/Solr 8.2), the
> Maven POMs were fixed: https://issues.apache.org/jira/browse/LUCENE-8993
> (Lucene/Solr
> 8.3)
>
>
>
> Sorry both links pointed to same diff. The history is above.
>
>
>
> So in short: to build
Sorry,
the Ivy build was fixed in <https://issues.apache.org/jira/browse/LUCENE-8807>
https://issues.apache.org/jira/browse/LUCENE-8807 (Lucene/Solr 8.2), the Maven
POMs were fixed: <https://issues.apache.org/jira/browse/LUCENE-8993>
https://issues.apache.org/jira/browse
ses, they keep broken. I changed this here
(possible since 8.3.0):
<https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a>
https://github.com/apache/lucene-solr/commit/4a015e224dcd4b1c5f3db92c01d8bf80be3c244a.
The Maven POMs were changed a bit later:
;https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
>>>
>>> http://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
>>> <https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
>>>
t.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
>> <https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
>>
>> http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
>> <https://maven.restlet.com
g/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
>
> http://maven.restlet.org/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
> <https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
>
> The error I get is a handshake failure which is
n.restlet.org/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar
<https://maven.restlet.com/org/restlet/jee/org.restlet/2.3.0/org.restlet-2.3.0.jar>
The error I get is a handshake failure which is a failure to connect
through the Maven java libraries. So, something about how they're hos
Let us find out and eliminate all uses of restlet from Solr. I don't think
we should be relying on any dependency that is not published to Maven
Central.
On Sat, 28 Dec, 2019, 12:32 AM Joel Bernstein, wrote:
> Ok, thanks.
>
> I'll dig around some more and see if I find a
should really post their stuff to Maven Central. No idea why they
> don't do this.
>
> Uwe
>
> Am December 27, 2019 6:54:04 PM UTC schrieb Joel Bernstein <
> joels...@gmail.com>:
>>
>> Yeah this a crazy way for them to manage dependencies.
>>
>
No idea. Complaint at them for breaking millions of builds.
They should really post their stuff to Maven Central. No idea why they don't do
this.
Uwe
Am December 27, 2019 6:54:04 PM UTC schrieb Joel Bernstein :
>Yeah this a crazy way for them to manage dependencies.
>
>I see t
Yeah this a crazy way for them to manage dependencies.
I see the old URL now redirects to https://maven.restlet.talend.com/.
I tried adding the repo to my POM as follows:
maven-restlet
Restlet repository
https://maven.restlet.talend.com
And still get
I figured out they again changed urls. No to talend.
This is a big issue and should reported that this horrible company, sorry! This
is a no go for maven dependencies. The reason is that Java handles redirection
in a bad way. So never ever change urls for branding purposes! Sorry Talked:
bad
to read artifact descriptor for
>org.restlet.jee:org.restlet:jar:2.3.0: Could not transfer artifact
>org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
>(http://maven.restlet.org): Received fatal alert: handshake_failure
>
>
>Has anyone ran into the restlet resolution is
r artifact
org.restlet.jee:org.restlet:pom:2.3.0 from/to maven-restlet
(http://maven.restlet.org): Received fatal alert: handshake_failure
Has anyone ran into the restlet resolution issues when resolving Solr
dependencies before and found the fix?
Joel Bernstein
http://joelsolr.blogspot.com/
Hi, I am running Solr 8.2 on a Maven project.
When opening my project in the browser, it shows the following console error:
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.solr.util.tracing.GlobalTracer
I have seen that class must be found in the dependency
Buchnick)
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Pro
e *xercesImpl* dependency exists for everyone. Any idea
about what might be going on here?
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
>
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project:
ild from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
>
e the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project:
lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
&g
well on Linux and OSX ideally.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOL
from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
> Issue Type: Imp
by Gradle IDEA plugin).
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-1345
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Pro
.com/apache/lucene-solr/tree/jira/SOLR-13452_gradle_6 which is up
from a few days ago I believe.
If anyone pushes something to the previous branch on an update, I'll cherry
pick it to the latest branch for you if it helps.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow buil
/apache/lucene-solr/tree/jira/SOLR-13452_gradle_5
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/j
assing an ant builder classpath safely, a little cleanup. Will
see if we need another adjustment for osx and buildTest.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
>
n gradle 6 and are potentially unsafe now.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apac
mmit f2ed8a025c6fa1f613b78e2c20d4b8ded4f64b81 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_6 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f2ed8a0 ]
SOLR-13452: Fix ratSources perf issue.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
mmit 5f31c1f006d9c23aa18b7b2b28ef255e0cad65d1 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_6 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=5f31c1f ]
SOLR-13452: Finish this rename properly.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
that uses simple-xml (not released since 2013) that needs
stax2-api < 4.x while other deps ask for 4.x.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
>
; Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project:
mmit df362dc4445296ae50084d8e422f42f4de36115c in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_6 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=df362dc ]
SOLR-13452: Improve some issues with eclipse support.
> Update the lucene-solr build from I
mmit f40a93619f7f591e48ad765097c603539da71faa in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_6 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f40a936 ]
SOLR-13452: Match src dir rename.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
e-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
>
mmit 758500bc686d5549c3b989f3d3275d63e4dbad4f in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_6 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=758500b ]
SOLR-13452: Fix OSX permission issue.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
Build: https://builds.apache.org/job/Lucene-Solr-Maven-master/2661/
No tests ran.
Build Log:
[...truncated 18338 lines...]
BUILD FAILED
/home/jenkins/jenkins-slave/workspace/Lucene-Solr-Maven-master/build.xml:673:
The following error occurred while executing this line:
/home/jenkins/jenkins
by Gradle IDEA plugin).
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-1345
; Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project:
mmit b49af883d52491b532df7689f64a700668efd749 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b49af88 ]
SOLR-13452: Fix OSX permission issue.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
mmit ff25fad1f3546aae129a3dc9614dfe9f0f080c8c in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=ff25fad ]
SOLR-13452: Fix ratSources perf issue.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
mmit f74c67c5b6533929417d66a803fab0257457447f in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from markrmiller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f74c67c ]
SOLR-13452: Finish this rename properly.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
that uses simple-xml (not released since 2013) that needs
stax2-api < 4.x while other deps ask for 4.x.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
>
mmit cbd34d64857e489287ebf05a3430b1fecf3c1dda in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=cbd34d6 ]
SOLR-13452: Match src dir rename.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
mmit 9c7699b97039da670f1ef1ae5a0c6e46f58a7767 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=9c7699b ]
SOLR-13452: Improve some issues with eclipse support.
> Update the lucene-solr build from I
n gradle 6 and are potentially unsafe now.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apac
e-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
>
bit more, rename TestEnforcers to TestChecks.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.or
ke a move from api to implementation.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.or
mmit 112ec90d6815014ece960f7ac0d017eb3e15599e in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=112ec90 ]
SOLR-13452: Improve max jvm default calculation.
> Update the lucene-solr build from I
lucene-solr build from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
>
mmit b8d97e78e2a0f2b84722051c0ea9b3c50b7040b1 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=b8d97e7 ]
SOLR-13452: Clean up.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow buil
mmit f24c6fc1c53aa24d8dd6bba888fd5e24e88512f8 in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=f24c6fc ]
SOLR-13452: Stub out lucene-luke and lucene-monitor.
> Update the lucene-solr build from I
ild from Ivy+Ant+Maven (shadow build) to Gradle.
> -
>
> Key: SOLR-13452
> URL: https://issues.apache.org/jira/browse/SOLR-13452
> Project: Solr
>
mmit 2711df79883d09f1388590ab8678864102c222cc in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=2711df7 ]
SOLR-13452: Clean up eclipse errors.
> Update the lucene-solr build from Ivy+Ant+Maven (
mmit 63be7b8292f39bed7596f46a2bf9d1fe322bf09a in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=63be7b8 ]
SOLR-13452: Fix spelling typo.
> Update the lucene-solr build from Ivy+Ant+Maven (shad
mmit 01866d81933d3ff1fa2d675e463a2f7051bbed6f in lucene-solr's branch
refs/heads/jira/SOLR-13452_gradle_5 from Mark Robert Miller
[ https://gitbox.apache.org/repos/asf?p=lucene-solr.git;h=01866d8 ]
SOLR-13452: Fix warnings.
> Update the lucene-solr build from Ivy+Ant+Maven (shadow buil
1 - 100 of 3514 matches
Mail list logo
