[Git][java-team/pkg-java-blog][master] new post: Help the Java Team distribute your project!

[Hans-Christoph Steiner]

Hans-Christoph Steiner pushed to branch master at Debian Java Maintainers / pkg-java-blog


Commits:
6478e9c1 by Hans-Christoph Steiner at 2019-02-01T12:43:07Z
new post: Help the Java Team distribute your project!

- - - - -


1 changed file:

- + content/2019/help-the-java-team-distribute-your-project.md


Changes:

=====================================
content/2019/help-the-java-team-distribute-your-project.md
=====================================
@@ -0,0 +1,41 @@
+Title: Help the Java Team distribute your project!
+Slug: help-the-java-team-distribute-your-project
+Date: 2019-01-31 14:00
+Authors: Hans-Christoph Steiner
+Tags: java
+Status: published
+
+There is a vast array of great free software projects written in Java.
+All sorts of large systems that we all rely on every day are built
+upon the [Apache Foundation libraries](https://projects.apache.org).
+Large companies like [Google](https://github.com/google/guava) and
+[IBM](https://developer.ibm.com/articles/cl-open-architecture-update/)
+put out standard libraries that so many other projects use.
+Unfortunately, the standard practice for distributing Java code makes
+it a lot of work to integrate them into Debian.
+
+The Debian Java Team's work is generally under-appreciated, so we are
+getting the word out here. The Java Team has to consistently fight the
+Java standard practice of bundling all deps into a single JAR.  This
+means there is no shared security updates, each dev has to update
+every dependency themselves in that model.  That works great for large
+companies with staff devoted to doing that.
+
+For the majority of Debian use cases, that works poorly.  Debian
+delivers on the promise that people can just `apt install foo` and
+have it work, and receive security updates.  The user does not even
+need to know what language the program is written in, it just works.
+
+The Java developer community need to embrace the value of these use
+cases, and help Debian by making it easier to package Java projects in
+the standard distro method, with shared dependencies that are
+independently updated.
+
+Python and Ruby provide great examples of more flexible standard
+practice for shipping software.  Both have methods of describing the
+dependencies needed, and then automatically fetching them.  They are
+designed in a way that is quite easy to hook into the native build
+system and make Debian packages.  That is sadly not the case with
+_Gradle_ and _Maven_, the most popular build systems for Java.  For
+those, the Java Team usually has to extensively patch the build system
+to make it work for the Debian package.



View it on GitLab: https://salsa.debian.org/java-team/pkg-java-blog/commit/6478e9c1818b92945eec114ea8ba7631f2aab2d9

-- 
View it on GitLab: https://salsa.debian.org/java-team/pkg-java-blog/commit/6478e9c1818b92945eec114ea8ba7631f2aab2d9
You're receiving this email because of your account on salsa.debian.org.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-java-commits/attachments/20190201/aa5a4161/attachment.html>