From: "Miroslav Šulc" <fordfrog@gentoo.org>
To: gentoo-soc@lists.gentoo.org
Subject: Re: [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 6
Date: Tue, 14 Jul 2020 07:03:37 +0200 [thread overview]
Message-ID: <d673b010-29cf-adb4-b1a3-97bd0200373a@gentoo.org> (raw)
In-Reply-To: <CAMBJAAr5ax+NVGw_1QJjbTcy0BykQvpp9odZZrO6AFdNCQdFtA@mail.gmail.com>
Dne 13. 07. 20 v 5:20 Zhang Zongyu napsal(a):
> Miroslav Šulc <fordfrog@gentoo.org> 于2020年7月12日周日 下午11:59写道：
>> hi Zhongyu,
>>
>> thank you for the report! looks like a nice progress to me :-) is there
>> anything i could help you with?
> I think we may discuss about how to compare locally compiles jars and
> binjars, and how to emerge kotlin, scala and lombok source files.
there are tools that could help with the comparison:
https://wiki.gentoo.org/wiki/Java_Developer_Guide#Java_API_Check
imo there are two checks needed:
1) check whether the api is the same both for our binary and upstream
binary (that verifies no code is missing)
2) check whether all needed resources are included in our binary (that
verifies that all resources needed for runtime will be available)
there might also be changes in the manifest file but those might not be
that important in most cases imo
>> wrt java-virtuals/*, there was a request (from mgorny iirc) to get rid
>> of java-virtuals/*. imo the logic of java-virtuals should be preserved,
>> but the virtuals should be placed under dev-java/ and use a naming
>> template like this:
>>
>> virtual = dev-java/servlet-api
>> implementations = dev-java/tomcat-servlet-api,
>> dev-java/glassfish-servlet-api etc.
>>
>> also, is java-pkg-simple.eclass ready for the main tree? and if so, did
>> you consider to go through the review process of the eclass? it might
>> take some time to get through the process so it might be good to start
>> the process soon to not be blocked by the process later.
> Currently, there are few differences between the main tree version and
> the one in my overlay.
> Functions to deal with JAVA_RESOURCES and JAVA_TEST_SRC_DIR do not
> appear in java-pkg-simple now.
> I am not sure whether I should go through the review now, because
> there isn't so much progress for java-pkg-simple.
> So maybe I will not go through the review this week.
>
>> i also just pushed your commits to the main java-ebuilder repo.
>>
>> thank you for your work and best regards!
>>
>> miroslav
>>
>>
> Regards,
> Zhang Zongyu
>
next prev parent reply other threads:[~2020-07-14 5:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-12 15:42 [gentoo-soc] Weekly Report: Big Data Infrastructure and Maven Overlay in Week 6 Zhang Zongyu
2020-07-12 15:59 ` Miroslav Šulc
2020-07-13 3:20 ` Zhang Zongyu
2020-07-14 5:03 ` Miroslav Šulc [this message]
2020-07-12 18:12 ` Ján Zahornadský
2020-07-13 3:40 ` Zhang Zongyu
2020-07-13 0:43 ` Benda Xu
2020-07-13 3:50 ` Zhang Zongyu
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=d673b010-29cf-adb4-b1a3-97bd0200373a@gentoo.org \
--to=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