From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-java/eclipse-ecj/
Date: Thu, 18 May 2023 05:59:19 +0000 (UTC) [thread overview]
Message-ID: <1684389548.a327fea7811c6dd72054c75314e09e17d22b69cb.fordfrog@gentoo> (raw)
commit: a327fea7811c6dd72054c75314e09e17d22b69cb
Author: Volkmar W. Pogatzki <gentoo <AT> pogatzki <DOT> net>
AuthorDate: Wed May 17 12:11:38 2023 +0000
Commit: Miroslav Šulc <fordfrog <AT> gentoo <DOT> org>
CommitDate: Thu May 18 05:59:08 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=a327fea7
dev-java/eclipse-ecj: add github upstream metadata
Signed-off-by: Volkmar W. Pogatzki <gentoo <AT> pogatzki.net>
Closes: https://github.com/gentoo/gentoo/pull/31076
Signed-off-by: Miroslav Šulc <fordfrog <AT> gentoo.org>
dev-java/eclipse-ecj/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-java/eclipse-ecj/metadata.xml b/dev-java/eclipse-ecj/metadata.xml
index de58dba6e94e..218c1eb894a3 100644
--- a/dev-java/eclipse-ecj/metadata.xml
+++ b/dev-java/eclipse-ecj/metadata.xml
@@ -12,6 +12,9 @@ as a batch-compiler by running the ecj-3.x script, or it can be
used with Ant by using the -lib option to and and setting
-Dbuild.compiler=ecj
</longdescription>
+<upstream>
+ <remote-id type="github">eclipse-jdt/eclipse.jdt.core</remote-id>
+</upstream>
<use>
<flag name="ant">Support using ecj in Ant builds via <pkg>dev-java/ant-eclipse-ecj</pkg></flag>
</use>
next reply other threads:[~2023-05-18 5:59 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 5:59 Miroslav Šulc [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-31 12:57 [gentoo-commits] repo/gentoo:master commit in: dev-java/eclipse-ecj/ Arthur Zamarin
2025-10-28 7:54 Arthur Zamarin
2025-10-26 18:56 Sam James
2025-10-03 16:23 Sam James
2025-10-03 16:23 Sam James
2025-09-28 9:11 Miroslav Šulc
2025-09-28 9:11 Miroslav Šulc
2025-04-19 16:51 Miroslav Šulc
2025-01-10 0:31 Sam James
2024-12-07 13:25 Miroslav Šulc
2024-09-20 15:42 Miroslav Šulc
2024-09-19 8:45 Miroslav Šulc
2024-09-19 8:45 Miroslav Šulc
2024-05-22 9:31 Miroslav Šulc
2024-04-30 15:31 Sam James
2024-04-30 15:31 Sam James
2024-04-05 8:16 Miroslav Šulc
2024-04-03 8:45 Miroslav Šulc
2024-03-30 11:13 Arthur Zamarin
2024-03-30 8:51 Arthur Zamarin
2024-03-17 8:56 Miroslav Šulc
2024-03-12 9:34 Miroslav Šulc
2024-03-12 8:05 Sam James
2024-03-12 8:05 Sam James
2024-03-12 4:29 Ionen Wolkens
2024-03-12 4:29 Ionen Wolkens
2024-03-12 4:29 Ionen Wolkens
2024-03-12 4:29 Ionen Wolkens
2024-02-26 12:53 Miroslav Šulc
2024-02-26 10:46 Jakov Smolić
2024-02-26 10:46 Jakov Smolić
2024-01-24 9:03 Miroslav Šulc
2023-12-04 9:09 Miroslav Šulc
2023-11-24 11:14 Miroslav Šulc
2023-11-24 11:14 Miroslav Šulc
2023-11-20 7:54 Miroslav Šulc
2023-11-20 7:54 Miroslav Šulc
2023-11-20 7:54 Miroslav Šulc
2023-07-18 17:21 Sam James
2023-07-18 17:21 Sam James
2023-05-21 7:58 Miroslav Šulc
2023-05-18 5:59 Miroslav Šulc
2023-02-16 6:04 Sam James
2023-02-16 6:04 Sam James
2023-01-15 9:50 Miroslav Šulc
2022-11-12 2:39 Sam James
2022-11-11 21:16 Sam James
2022-10-11 18:25 Miroslav Šulc
2022-07-05 7:29 Agostino Sarubbo
2022-07-05 6:01 Agostino Sarubbo
2022-06-02 6:20 Miroslav Šulc
2022-05-30 8:36 Florian Schmaus
2022-05-11 7:33 Florian Schmaus
2022-05-10 13:32 Florian Schmaus
2022-05-01 16:34 Miroslav Šulc
2022-03-30 11:09 Jakov Smolić
2022-03-02 20:52 Miroslav Šulc
2022-03-02 20:52 Miroslav Šulc
2022-02-19 9:44 Miroslav Šulc
2022-02-02 15:23 Jakov Smolić
2021-11-17 12:06 Miroslav Šulc
2020-11-24 10:30 Miroslav Šulc
2020-09-19 15:55 Aaron Bauman
2020-02-27 22:35 Miroslav Šulc
2020-02-27 20:01 Miroslav Šulc
2019-10-16 10:51 Miroslav Šulc
2019-01-23 14:54 Miroslav Šulc
2016-12-13 11:30 Agostino Sarubbo
2016-12-13 11:05 Agostino Sarubbo
2016-02-19 20:54 James Le Cuirot
2015-12-04 17:56 Miroslav Šulc
2015-08-22 20:59 James Le Cuirot
2015-08-22 20:59 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=1684389548.a327fea7811c6dd72054c75314e09e17d22b69cb.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