From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 6C417138359 for ; Fri, 24 Jul 2020 13:29:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7EA11E081A; Fri, 24 Jul 2020 13:29:06 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 24400E081A for ; Fri, 24 Jul 2020 13:29:06 +0000 (UTC) Received: from [2a0c:b641:69c:e7f1:6d3:b0ff:fe40:5fd8] (port=50964 helo=robot) by muon with esmtp (Exim 4.92) (envelope-from ) id 1jyxkx-0003hh-9X for gentoo-soc@lists.gentoo.org; Fri, 24 Jul 2020 13:28:59 +0000 From: Benda Xu To: gentoo-soc@lists.gentoo.org Subject: Re: [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 7 References: Date: Fri, 24 Jul 2020 21:28:53 +0800 In-Reply-To: (Zhang Zongyu's message of "Mon, 20 Jul 2020 01:10:00 +0800") Message-ID: <87imednisq.fsf@robot.e.airelinux.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-soc@lists.gentoo.org Reply-to: gentoo-soc@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: text/plain X-Archives-Salt: ceaf3f3d-1186-4ac1-9cfb-9df428a97b67 X-Archives-Hash: 48388cee37c2cf61b8ca4ea3c4d0b781 Hi Zongyu, Zhang Zongyu writes: > This week I mostly worked on the java-pkg-simple.eclass.[1] > > I tried to make use of the variables listed in java-ebuilder, including > ${JAVA_TEST_SRC_DIRS}, ${JAVA_RESOURCES_DIRS}, > ${JAVA_MAIN_CLASS}, and so on. > Besides, there are two more variables in the eclass called > ${JAVA_BINJAR_FILENAME} and ${JAVA_LAUNCHER_FILENAME}. > ${JAVA_BINJAR_FILENAME} indicates the binary file that will be > compared with our natively compiled jar file, and it also enables the > possibility to install itself directly, which may help us avoid circular deps. > ${JAVA_LAUNCHER_FILENAME} specifies the name of the launcher > script for the jar, it works together with ${JAVA_MAIN_CLASS}. > You can test the new eclass by emerging "java-ebuilder::spark-overlay" > and "dev-java:commons-io:0". [2] Good. > Also, there are some bugfixes for java-ebuilder, which you can check in [3]. > > I hope that the eclass is working well and if it is going well we may start > to go through the review process this week. OK, please push through the review process ASAP. Yours, Benda