[gentoo-java][PR] ivy, mvn, sbt, gradle builders improvement for ebuild development

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--ln8yNG26V5V22o2Bf4XPZs3pg5WJaF8bT
Content-Type: multipart/mixed; boundary="QW8cQbftP7CCEft7hche8ePvdJ6oHO1F6";
 protected-headers="v1"
From: Samuel Bernardo <[email protected]>
To: Gentoo Java <[email protected]>
Cc: Gentoo Dev <[email protected]>
Message-ID: <[email protected]>
Subject: [gentoo-java][PR] ivy, mvn, sbt, gradle builders improvement for
 ebuild development

--QW8cQbftP7CCEft7hche8ePvdJ6oHO1F6
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US

Dear Java team,

I send this email to mention that it seems to be missing eclasses for
JVM builders such as those I mention in this email subject. Dependencies
and tasks management are hard tasks now that I think to have great scope
for improvement.

Looking into the developments made in go eclasses, there is a very
interesting solution in go-module.eclass with EGO_SUM to avoid the need
of additional tarballs to fulfill the network sandbox requirement. This
way, dependencies could be listed from files, optimizing the current
approach without requiring to distribute blinded dependency tarballs.

I also check java-ant-2.eclass to manage build tasks for ant. Would be
very useful to have eclass like this for the other builders.

Also review java-pkg-2.eclass and java-utils-2.eclass that are more
related to Java packages and ant builder. Seems more difficult than
usual to understand them and how to apply to other projects. Maybe to
turn this more friendly a java-common.eclass could be created for
example, collecting the common variables and functions such as
java-pkg_getjars and java-pkg_dojar, to reuse them with all JVM dialect
related projects.

Are you forging any solutions already to improve this kind of PR?

Thanks,

Samuel



--QW8cQbftP7CCEft7hche8ePvdJ6oHO1F6--

--ln8yNG26V5V22o2Bf4XPZs3pg5WJaF8bT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEnRraRmCmFBxzQ4tS7Y2pzb+rOzkFAl6Qj1sACgkQ7Y2pzb+r
OzlcLg//XBSvYVZGCTxnU06hiU5aaYgoRR42WNEhamnbvC36kw0l4NCTaxIqqsZ3
1c0fYDeAYtsTcn+o4HNj70CDQGuFVtTDoldp5Aum6SsTqrbd4w0LABw8RiVo6YlB
v7yzH5mvVDds+PSHfkLViiaJNtfeE6bwXLFpnnhHrO1zax5N0GPSAEeOLIxnXSLS
YzSRLLB64Ug3JycUzLM9nK+Yu73a0yia9GSD9ptdShXuQAsT9XUArzz9VmicedYE
HVpogWAYF5ocROSa+8tjUIWAxcnWIP25xonQFSluhvX/aF4NVroMTZXBhxLPcF3A
TSpFLZp37X0TfcvPgnn5sEwO0c9FxPLdJ9s30pvCXOObz89ufdy+JemKpR7iNj9B
auWEgQAQynrp/9p5KALWt6JjQ+NjKvyPqrqo7bMwOWdW8q3xLnP5sy3oKUQ0xOwu
ZNzTdj2AJklTdyTurkuE97HL4K05nnWrCKaYAt9xhCqh/LppwZexeDgSAT79Mtwh
W8B/Mver3YUcHP4UtyxcRBNTjGv18klJr4QEOqIQZs+VLneoLkubz0o2XbuSuzhq
yGPSo4+616ee+b/DdFzTjNA0XeIOWol0ammGispWu2dzHBzwP5UDRKJ3LXsXZZ2i
zxtu08qgTX26ZeUyZ8cSq2sdpYm3ln2qh2paC+3y3Kh26IKBDUg=
=YNY/
-----END PGP SIGNATURE-----

--ln8yNG26V5V22o2Bf4XPZs3pg5WJaF8bT--