Path: csiph.com!aioe.org!.POSTED.xV/6gj+grSZn0+TB/DGTcw.user.gioia.aioe.org!not-for-mail From: Graeme Geldenhuys Newsgroups: comp.lang.java.programmer Subject: Re: Preferred way to distribute application Date: Wed, 10 Apr 2019 10:29:07 +0100 Organization: Aioe.org NNTP Server Lines: 31 Message-ID: References: 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 X-Notice: Filtered by postfilter v. 0.9.2 Content-Language: en-GB Xref: csiph.com comp.lang.java.programmer:38889 Thanks for your time and feedback Joerg. On 08/04/2019 13:46, Joerg Meier wrote: >> 1. Package everything into a single JAR with embedded jar >> dependencies. > > This is by far the best default way if you want to distribute a runnable > application. This is what I was using up to now. Glad to hear I was on the right track. >> At the moment I don't have a lot of dependencies, but you never know >> what the future of the project might dictate. > > You pretty much SHOULD be using dependencies. One of Javas biggest > strengths is the huge, high quality ecosystem that allows you to not > reinvent wheels and instead focus on your unique sell points inspead of Coming from Object Pascal (Delphi/FPC) that is a rather large change for me. The ecosystem in Object Pascal is really a drop in the ocean compared to Java, and often I rolled-my-own solution in Object Pascal projects. Indeed in Java it seems somebody has already written an excellent library to reuse. I've quick discovered this when I wanted to handle command line parameters, processing JSON files or producing PDF output. Brilliant and well supported libraries already existed for all of those. It saved me a huge amount of time. Regards, Graeme