From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Cc: fordfrog@gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 5
Date: Mon, 06 Jul 2020 09:09:44 +0800 [thread overview]
Message-ID: <87v9j1sb3b.fsf@robot.e.airelinux.org> (raw)
In-Reply-To: <CAMBJAAqUGJy0WGqsp1MHAEhi+OzCuEqxT2o5Sn36P=5H8N-Taw@mail.gmail.com> (Zhang Zongyu's message of "Mon, 6 Jul 2020 00:05:00 +0800")
Zhang Zongyu <zzy2529420793@gmail.com> writes:
> This week I have done a lot of repetitive work. That is, to go through
> all of the ebuild files in Gentoo Repository and to get them the
> equivalent GroupId and ArtifactId in Maven Central. There are more
> than 500 packages in dev-java/ and java-virtual/ category, and
> sometimes one Gentoo package may correspond to more than one Maven
> artifact, so it took me a lot of time to complete them. And here is my
> lookup up table which covers all packages in dev-java/ and maps
> "category/package:slot" into "groupId:artifactId".[1] As a result,
> spark-core can make use of more than 100 Gentoo native packages now.
My previous approach was to `ebuild xxxx prepare` the packages in
::gentoo and inspect the pom.xml file inside ${WORKDIR}. Does that work
for you?
https://github.com/gentoo/java-ebuilder/blob/master/scripts/meta.sh
> Besides, I have also added java-ebuilder some features. It can check
> the metadata of a package and get the correct SLOT, and it can make
> ebuild unpack "Maven Central distributed source files" into proper
> ${JAVA_SRC_DIR} now.
Good!
> Next week I am going to test and add jaxb (javax.xml.bind:jaxb-api and
> javax.xml.bind:jaxb-impl) and some newer version packages which are
> required by spark-core, and
Good to know we are getting back jaxb. It is strange to me that without
such a seemingly central package packages in ::gentoo still work. Is it
now part of icedtea jdk? Please dig more into the story behind jaxb in
the #gentoo-java IRC and bugzilla.
Maybe fordfrog have a better answer (@fordfrog, not sure if you have
subscribed to gentoo-soc, I am Ccing you).
> I hope the newer version ebuild files could be accepted by Gentoo-Java
> team. The prototype of the ebuild files that are just generated by
> java-ebuilder are listed in [2].
Please start the code review processes of the new java packages by
submitting bug reports and pull requests when you see fit.
Benda
> [1] lookup table containing all packages from dev-java/
> https://github.com/6-6-6/JEbuilder/blob/master/app-portage/java-ebuilder/files/scripts/LUT/LUT
> [2] a prototype overlay
> https://github.com/6-6-6/spark-overlay/tree/master/dev-java
next prev parent reply other threads:[~2020-07-06 1:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 16:05 [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 5 Zhang Zongyu
2020-07-05 16:18 ` EBo
2020-07-05 17:23 ` Zhang Zongyu
2020-07-05 17:40 ` EBo
2020-07-06 1:09 ` Benda Xu [this message]
2020-07-06 8:26 ` Miroslav Šulc
2020-07-06 8:42 ` Miroslav Šulc
2020-07-06 9:58 ` Zhang Zongyu
2020-07-06 10:26 ` Benda Xu
2020-07-06 10:28 ` Miroslav Šulc
2020-07-06 10:58 ` Miroslav Šulc
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=87v9j1sb3b.fsf@robot.e.airelinux.org \
--to=heroxbd@gentoo.org \
--cc=fordfrog@gentoo.org \
--cc=gentoo-soc@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