Path: csiph.com!aioe.org!.POSTED.xV/6gj+grSZn0+TB/DGTcw.user.gioia.aioe.org!not-for-mail
From: Graeme Geldenhuys <graemeg@example.net>
Newsgroups: comp.lang.java.programmer
Subject: Preferred way to distribute application
Date: Mon, 8 Apr 2019 12:28:17 +0100
Organization: Aioe.org NNTP Server
Lines: 25
Message-ID: <q8fb8g$243$1@gioia.aioe.org>
NNTP-Posting-Host: xV/6gj+grSZn0+TB/DGTcw.user.gioia.aioe.org
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Complaints-To: abuse@aioe.org
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
Content-Language: en-GB
X-Mozilla-News-Host: news://nntp.aioe.org:119
X-Notice: Filtered by postfilter v. 0.9.2
Xref: csiph.com comp.lang.java.programmer:38880

What is the preferred way to distribute a console java application?

For example:

  1.  Package everything into a single JAR with embedded jar
      dependencies.

  2.  Package application into a single JAR but don't embed any
      dependency jars. Have the dependency jars as a separate
      downloadable archive.

  3.  Package everything into a single JAR with related
      dependencies but dependencies are unpacked - seems to
      produce a slightly smaller final jar.


At the moment I don't have a lot of dependencies, but you never know
what the future of the project might dictate.

Not sure if it matters, but I'm using Eclipse to build the final JAR. In
the future I would like to let Maven do this for me so I can automate
builds.

Regards,
  Graeme