From: "Sven Wegener" <swegener@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/commons-logging/
Date: Tue, 21 Mar 2023 09:06:06 +0000 (UTC) [thread overview]
Message-ID: <1679389480.dd148ddaee31bc22dad53bd86f3d42bbd9b03539.swegener@gentoo> (raw)
commit: dd148ddaee31bc22dad53bd86f3d42bbd9b03539
Author: Sven Wegener <swegener <AT> gentoo <DOT> org>
AuthorDate: Tue Mar 21 08:59:15 2023 +0000
Commit: Sven Wegener <swegener <AT> gentoo <DOT> org>
CommitDate: Tue Mar 21 09:04:40 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=dd148dda
dev-java/commons-logging: remove stray url from global scope
Bug: https://bugs.gentoo.org/902121
Signed-off-by: Sven Wegener <swegener <AT> gentoo.org>
dev-java/commons-logging/commons-logging-1.3.0_pre20230319.ebuild | 1 -
1 file changed, 1 deletion(-)
diff --git a/dev-java/commons-logging/commons-logging-1.3.0_pre20230319.ebuild b/dev-java/commons-logging/commons-logging-1.3.0_pre20230319.ebuild
index 548d30669d48..b478d6426af2 100644
--- a/dev-java/commons-logging/commons-logging-1.3.0_pre20230319.ebuild
+++ b/dev-java/commons-logging/commons-logging-1.3.0_pre20230319.ebuild
@@ -82,7 +82,6 @@ src_compile() {
popd > /dev/null || die
}
-https://github.com/apache/commons-logging/blob/058cf5ee350cd83d1ab28b000ad6be903ca160c5/pom.xml#L396-L407
src_test() {
# Do not run Log4j tests because these tests use an Appender to verify
# logging correctness. The log4j-12-api bridge no longer supports using an
next reply other threads:[~2023-03-21 9:06 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 9:06 Sven Wegener [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-12-30 19:41 [gentoo-commits] repo/gentoo:master commit in: dev-java/commons-logging/ Florian Schmaus
2024-12-23 23:47 Jakov Smolić
2024-11-15 22:13 Sam James
2024-10-17 9:05 Miroslav Šulc
2024-10-16 9:39 Miroslav Šulc
2024-05-20 7:50 Miroslav Šulc
2024-05-19 17:40 Arthur Zamarin
2024-05-18 3:51 Sam James
2024-05-18 3:19 Sam James
2024-05-18 3:19 Sam James
2024-04-18 10:56 Miroslav Šulc
2023-04-20 5:01 Sam James
2023-04-20 5:01 Sam James
2023-04-20 4:14 Arthur Zamarin
2023-04-20 4:02 Sam James
2023-03-21 6:11 Miroslav Šulc
2023-03-19 6:20 Miroslav Šulc
2022-10-14 17:41 Miroslav Šulc
2022-03-31 18:58 Arthur Zamarin
2022-03-31 16:47 Arthur Zamarin
2022-03-30 11:47 Agostino Sarubbo
2022-03-30 11:09 Jakov Smolić
2022-03-30 11:09 Jakov Smolić
2022-02-26 11:53 Arthur Zamarin
2022-02-26 8:52 Miroslav Šulc
2022-02-25 18:53 Arthur Zamarin
2022-02-24 9:47 Miroslav Šulc
2022-01-27 8:17 Miroslav Šulc
2021-05-16 18:58 Sam James
2021-05-09 10:02 Miroslav Šulc
2021-05-09 9:17 Agostino Sarubbo
2021-05-06 7:22 Sergei Trofimovich
2021-05-01 18:19 Agostino Sarubbo
2021-04-25 9:18 Sergei Trofimovich
2021-04-21 10:00 Miroslav Šulc
2021-04-21 10:00 Miroslav Šulc
2021-04-21 10:00 Miroslav Šulc
2021-04-19 17:57 Miroslav Šulc
2018-04-14 21:04 Patrice Clement
2018-02-16 22:35 Patrice Clement
2018-02-16 10:27 Patrice Clement
2017-08-28 22:01 James Le Cuirot
2017-08-28 22:01 James Le Cuirot
2017-07-13 12:13 Alexis Ballier
2017-02-24 0:34 Michael Weber
2016-04-26 21:47 James Le Cuirot
2015-08-30 19:34 Patrice Clement
2015-08-30 19:34 Patrice Clement
2015-08-26 14:17 Mikle Kolyada
2015-08-16 20:52 Mikle Kolyada
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=1679389480.dd148ddaee31bc22dad53bd86f3d42bbd9b03539.swegener@gentoo \
--to=swegener@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