public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/lucene/
Date: Tue, 10 Sep 2024 19:11:35 +0000 (UTC)	[thread overview]
Message-ID: <1725995475.e1d13e8e5bc9400061795a9c4d2eb1088f770f85.fordfrog@gentoo> (raw)

commit:     e1d13e8e5bc9400061795a9c4d2eb1088f770f85
Author:     Volkmar W. Pogatzki <gentoo <AT> pogatzki <DOT> net>
AuthorDate: Tue Sep 10 07:52:54 2024 +0000
Commit:     Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Tue Sep 10 19:11:15 2024 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=e1d13e8e

dev-java/lucene: add comment about not using eant for tests

Signed-off-by: Volkmar W. Pogatzki <gentoo <AT> pogatzki.net>
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>

 dev-java/lucene/lucene-2.4.1-r5.ebuild | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/dev-java/lucene/lucene-2.4.1-r5.ebuild b/dev-java/lucene/lucene-2.4.1-r5.ebuild
index a3429854eef1..2a1641800238 100644
--- a/dev-java/lucene/lucene-2.4.1-r5.ebuild
+++ b/dev-java/lucene/lucene-2.4.1-r5.ebuild
@@ -65,6 +65,8 @@ src_compile() {
 }
 
 src_test() {
+	# we found that running tests with eant creates completely different output than
+	# runnning with ant. no idea what exactly is causing that difference,
 	ant test-core
 }
 


             reply	other threads:[~2024-09-10 19:11 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-10 19:11 Miroslav Šulc [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-09-10 19:11 [gentoo-commits] repo/gentoo:master commit in: dev-java/lucene/ Miroslav Šulc
2024-09-10  6:46 Miroslav Šulc
2022-04-23  7:05 Miroslav Šulc
2022-04-22 18:10 Arthur Zamarin
2022-04-22 18:10 Arthur Zamarin
2022-03-15 23:20 Sam James
2022-03-15 17:23 Sam James
2021-06-11  8:33 Miroslav Šulc
2020-05-04 22:43 Jonas Stein
2018-11-04 13:50 Pacho Ramos
2018-04-18 14:13 Aaron Bauman
2018-03-17 13:37 Pacho Ramos
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2018-01-03 10:08 Patrice Clement
2017-04-08 21:57 Patrice Clement
2016-04-07  9:26 James Le Cuirot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1725995475.e1d13e8e5bc9400061795a9c4d2eb1088f770f85.fordfrog@gentoo \
    --to=fordfrog@gentoo.org \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox