public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Benda Xu <heroxbd@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 5
Date: Mon, 06 Jul 2020 18:26:46 +0800	[thread overview]
Message-ID: <87k0zhlz15.fsf@robot.e.airelinux.org> (raw)
In-Reply-To: <CAMBJAApgoRuuM=6=V8VZ_Nu0v7O5tynF_A43GkOTL0cMdC5xLQ@mail.gmail.com> (Zhang Zongyu's message of "Mon, 6 Jul 2020 17:58:00 +0800")

Zhang Zongyu <zzy2529420793@gmail.com> writes:

>> do these work with java-pkg-simple.eclass as is in the tree or it needs
>> your updated eclass?
>
> The class is modified by me. It can be found here[1]. The major
> differences are the way to process JAVA_*_CLASSPATH variables and a
> new variable called "JAVA_NEEDS_TOOLS".
>
>> getting the changes in the eclass into the main tree requires review and approval by devs.
>
> Is it correct that I should trigger the review via bugs.gentoo.org?

Initiate the eclass patch review by starting a thread in
gentoo-dev@l.g.o.   `git format-patch` and `git send-email` are good
tools for this purpose.

>> also, before getting the ebuilds into the tree, i would really like to
>> see an automated test to verify that the content of our jar files
>> matches the content of the maven repo jar files. without this, we might
>> get issues because of missing resources and maybe even other causes.

> Currently, I do not have a clear way of reaching the goal...
> A preliminary thought is to maintain a modified version of java-pkg-simple.
> The modified eclass will automatically compare the files in postinst phase.
> I will try to work out it this week.

I think src_test() is better than pkg_postinst().

Benda


  reply	other threads:[~2020-07-06 10:26 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
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 [this message]
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=87k0zhlz15.fsf@robot.e.airelinux.org \
    --to=heroxbd@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