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
signature.asc
Description: OpenPGP digital signature
