glimmer-dsl-swt 4.20.16.0 → 4.21.0.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 82d9785cf890715947534ab665bf4f821cd79d67149e5bf7eb98d461d6457e46
-  data.tar.gz: 89ca9c71b72d865b69b526f3a9f7c1745e38df226ca32a71d800e34e80c35228
+  metadata.gz: 5cdb03595910fbb0a4e8a6e40262aea904904063f08e8cf6144bb5569408fc60
+  data.tar.gz: efe9220cb985da71aa1c27efc914cdd9d71d21a0466adad994d0e751c3063219
 SHA512:
-  metadata.gz: 76f88567594af281b05b30a521ec609c8b6ac305870addcd7e018f3cdbae79f1dc7d415900cc047057e4f3f970f14c2f4b46a5db4fa8ede29957d4b1ce42effc
-  data.tar.gz: fa5ee13574ea2c71de9e0d285ff3b4f3a9eea2e068292e6f7b86908f2b1d69e8412e40db28b68d4df9f93dab9ce749e41e50431fccbdbff141a28062330d1f0a
+  metadata.gz: 516f678f951f896a4421f1dbb46bb6b7c5e2c53713892627e6c3d51f097f74f50328d82582a04c33db786cdf6c71a7de0afc89299f34262b8e5af99b18e2429c
+  data.tar.gz: 11ce0f19287bc04ff2f1824896400d8ed90061a738960d8495131245ebefdd9e1dfd04868f4a8ef4a9ada9a7c16654a5f035a6d92a88bbf8296c23f832bbb892

data/CHANGELOG.md

@@ -1,8 +1,13 @@
 # Change Log
 
-### 4.20.16.0
-
-- Fix API of `Glimmer::Launcher` by renaming `#application_paths` to `#application_path`
+### 4.21.0.0
+
+- Upgrade to SWT 4.21
+- Upgrade to JDK 16.0.2
+- Upgrade to JRuby 9.3.0.0
+- Update packaging to rely on JDK 16 `jpackage` (instead of older JDK 8 `javapackager`)
+- Renamed `Glimmer::RakeTask::Package.javapackager_extra_args` to `Glimmer::RakeTask::Package.jpackage_extra_args` to match the name of `jpackage` in JDK 16
+- Change `package/[os]` scaffolding placement for packaging icons into `icons/[os]` to accomodate Java 9 Module security for icon retrieval from within a JAR
 
 ### 4.20.15.5
 

data/README.md

@@ -1,4 +1,4 @@
-# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for SWT 4.20.16.0
+# [<img src="https://raw.githubusercontent.com/AndyObtiva/glimmer/master/images/glimmer-logo-hi-res.png" height=85 />](https://github.com/AndyObtiva/glimmer) Glimmer DSL for SWT 4.21.0.0
 ## JRuby Desktop Development GUI Framework
 [![Gem Version](https://badge.fury.io/rb/glimmer-dsl-swt.svg)](http://badge.fury.io/rb/glimmer-dsl-swt)
 [![Travis CI](https://travis-ci.com/AndyObtiva/glimmer-dsl-swt.svg?branch=master)](https://travis-ci.com/github/AndyObtiva/glimmer-dsl-swt)
@@ -15,7 +15,7 @@
 [<img src="https://covers.oreillystatic.com/images/9780596519650/lrg.jpg" width=105 /><br />
 Featured in JRuby Cookbook](http://shop.oreilly.com/product/9780596519650.do) and [Chalmers/Gothenburg University Software Engineering Master's Lecture Material](http://www.cse.chalmers.se/~bergert/slides/guest_lecture_DSLs.pdf)
 
-[Glimmer DSL for SWT](https://rubygems.org/gems/glimmer-dsl-swt) 4.20.16.0 includes [SWT 4.20](https://download.eclipse.org/eclipse/downloads/drops4/R-4.20-202106111600/), which was released on June 11, 2021. Gem version numbers are in sync with the SWT library versions. The first two digits represent the SWT version number. The last two digits represent the minor and patch versions of Glimmer DSL for SWT. Note that SWT now supports AARCH64 on Mac and Linux, but it is not fully tested in Glimmer DSL for SWT yet, so deem its support experimental for the time being without guarantees for functionality until declared otherwise (please report any issues you may encounter).
+[Glimmer DSL for SWT](https://rubygems.org/gems/glimmer-dsl-swt) 4.21.0.0 includes [SWT 4.21](https://download.eclipse.org/eclipse/downloads/drops4/R-4.21-202109060500/), which was released on September 6, 2021. Gem version numbers are in sync with the SWT library versions. The first two digits represent the SWT version number. The last two digits represent the minor and patch versions of Glimmer DSL for SWT. Note that SWT now supports AARCH64 on Mac and Linux, but it is not fully tested in Glimmer DSL for SWT yet, so deem its support experimental for the time being without guarantees for functionality until declared otherwise (please report any issues you may encounter).
 
 **Starting in version 4.20.0.0, [Glimmer DSL for SWT](https://rubygems.org/gems/glimmer-dsl-swt) comes with the new [***Shine***](/docs/reference/GLIMMER_GUI_DSL_SYNTAX.md#shine) syntax** for highly intuitive and visually expressive View/Model Attribute Mapping, relying on `<=>` for bidirectional (two-way) data-binding and `<=` for unidirectional (one-way) data-binding, providing an alternative to the `bind` keyword (keep in mind that it is still a beta, so default back to `bind` whenever needed).
 
@@ -290,10 +290,10 @@ https://www.eclipse.org/swt/faq.php
 
 ## Pre-requisites
 
-- JDK 8u241 (1.8.0_241) (find at https://www.oracle.com/java/technologies/javase/javase8u211-later-archive-downloads.html / On Windows, ensure PATH includes Java bin directory  like C:\Program Files\Java\jdk1.8.0_241\bin for javapackager to work during packaging Glimmer applications)
+- JDK 16 (16.0.2) (find at https://www.oracle.com/java/technologies/downloads/#java16 / On Windows, ensure PATH includes Java bin directory for jpackage to work during packaging Glimmer applications)
 - [RVM](http://rvm.io) on Mac & Linux (not available on Windows)
-- JRuby 9.2.19.0 (supporting Ruby 2.5.x syntax) (get via [RVM](http://rvm.io) on Mac and Linux by running `rvm install jruby-9.2.19.0`; On Windows, find at [https://www.jruby.org/download](https://www.jruby.org/download))
-- SWT 4.20 (already included in the [glimmer-dsl-swt](https://rubygems.org/gems/glimmer-dsl-swt) gem). Note that SWT now supports AARCH64 on Mac and Linux, but it is not fully tested with Glimmer DSL for SWT yet, so it is considered experimental until declared otherwise.
+- JRuby 9.3.0.0 (supporting Ruby 2.6.x syntax) (get via [RVM](http://rvm.io) on Mac and Linux by running `rvm install jruby-9.3.0.0`; On Windows, find at [https://www.jruby.org/download](https://www.jruby.org/download) [you might have to dual-install JDK8 temporarily as it might be required by jruby installer and then switch JAVA_HOME to JDK16 once done installing and restart command prompt/git bash])
+- SWT 4.21 (already included in the [glimmer-dsl-swt](https://rubygems.org/gems/glimmer-dsl-swt) gem). Note that SWT now supports AARCH64 on Mac and Linux, but it is not fully tested with Glimmer DSL for SWT yet, so it is considered experimental until declared otherwise.
 - Git (comes with Mac and Linux. Install on Windows: https://git-scm.com/download/win )
 
 Glimmer might still work on other versions of Java, JRuby and SWT, but there are no guarantees, so it is best to stick to the pre-requisites outlined above.
@@ -322,7 +322,7 @@ jgem install glimmer-dsl-swt
 
 Or this command if you want a specific version:
 ```
-jgem install glimmer-dsl-swt -v 4.20.16.0
+jgem install glimmer-dsl-swt -v 4.21.0.0
 ```
 
 `jgem` is JRuby's version of `gem` command.
@@ -337,7 +337,7 @@ On the Mac, you also have to run:
 glimmer-setup
 ```
 
-This ensures configuring extra required Mac options before using `glimmer` and `girb` commands.
+This ensures configuring required Mac jruby options before using `glimmer` and `girb` commands (adding `export JRUBY_OPTS="$JRUBY_OPTS -J-XstartOnFirstThread"` to `~/.zprofile` and `~/.bash_profile`).
 
 If you are new to Glimmer and would like to continue learning the basics, you may continue to the [Glimmer Command](#glimmer-command) section.
 
@@ -350,7 +350,7 @@ Note: if you're using activerecord or activesupport, keep in mind that Glimmer u
 
 Add the following to `Gemfile`:
 ```
-gem 'glimmer-dsl-swt', '~> 4.20.16.0'
+gem 'glimmer-dsl-swt', '~> 4.21.0.0'
 ```
 
 And, then run:
@@ -371,7 +371,7 @@ glimmer
 ```
 
 ```
-Glimmer (JRuby Desktop Development GUI Framework) - JRuby Gem: glimmer-dsl-swt v4.20.16.0
+Glimmer (JRuby Desktop Development GUI Framework) - JRuby Gem: glimmer-dsl-swt v4.21.0.0
       
 Usage: glimmer [--bundler] [--pd] [--quiet] [--debug] [--log-level=VALUE] [[ENV_VAR=VALUE]...] [[-jruby-option]...] (application.rb or task[task_args]) [[application2.rb]...]
 

data/RUBY_VERSION

@@ -1 +1 @@
-jruby-9.2.19.0
+jruby-9.3.0.0

data/VERSION

@@ -1 +1 @@
-4.20.16.0
+4.21.0.0

data/docs/reference/GLIMMER_PACKAGING_AND_DISTRIBUTION.md

@@ -1,8 +1,8 @@
 ## Glimmer Packaging and Distribution
 
-Note: this section mostly applies to Mac and Windows. On Linux, you can just run `glimmer package:gem` and after installing the gem, you get an executable matching the name of the app/custom-shell-gem you are building (e.g. `calculator` command becomes available after installing the [glimmer-cs-calculator](https://github.com/AndyObtiva/glimmer-cs-calculator) gem). On Windows, ensure system PATH includes Java bin directory like "C:\Program Files\Java\jdk1.8.0_241\bin" for javapackager command to work during packaging Glimmer applications.
+Note: this section mostly applies to Mac and Windows. On Linux, you can just run `glimmer package:gem` and after installing the gem, you get an executable matching the name of the app/custom-shell-gem you are building (e.g. `calculator` command becomes available after installing the [glimmer-cs-calculator](https://github.com/AndyObtiva/glimmer-cs-calculator) gem). On Windows, ensure system PATH includes Java bin directory `"C:\Program Files\Java\jdk-16.0.2\bin"` at the top for `jpackage` command to work during packaging Glimmer applications.
 
-Note 2: Glimmer packaging has a strong dependency on JDK8 at the moment. JDK9 & JDK10 might work, but JDK11 and onward definitely won't since they dropped javapackager, which later came back as jpackage in JDK14, but it's not ready for prime time yet. Just stick to JDK8 for now, strongly supported by Oracle for the next 6 years at least.
+Note 2: Glimmer packaging has a strong dependency on JDK16 since it includes the packaging tool `jpackage`.
 
 Glimmer simplifies the process of native-executable packaging and distribution on Mac and Windows via a single `glimmer package` command:
 
@@ -10,9 +10,7 @@ Glimmer simplifies the process of native-executable packaging and distribution o
 glimmer package
 ```
 
-It works out of the box for any application scaffolded by [Glimmer Scaffolding](#scaffolding), generating all available packaging types on the current platform (e.g. `DMG`, `PKG`, `APP` on the Mac) and displaying a message indicating what pre-requisite setup tools are needed if not installed already (e.g. [Wix Toolset](https://wixtoolset.org/) to generate MSI files on Windows). If you install Wix, make sure it is on the system PATH by adding for example "C:\Program Files (x86)\WiX Toolset v3.11\bin" to the Windows Environment Variables.
-
-(note: if you see this error on the Mac 'Error: Bundler "DMG Installer" (dmg) failed to produce a bundle.', ignore it as it should have produced a bundle anyways. It is a harmless issue in 3rd party dependency: javapackager.)
+It works out of the box for any application scaffolded by [Glimmer Scaffolding](#scaffolding), generating default packaging type on the current platform if not specified (i.e. `app-image`) and displaying a message indicating what pre-requisite setup tools are needed if not installed already (e.g. [Wix Toolset](https://wixtoolset.org/) to generate MSI files on Windows). If you install Wix, make sure it is on the system PATH by adding for example "C:\Program Files (x86)\WiX Toolset v3.11\bin" to the Windows Environment Variables.
 
 You may choose to generate a specific type of packaging instead by addionally passing in the `[type]` option. For example, this generates an MSI setup file on Windows:
 
@@ -20,14 +18,21 @@ You may choose to generate a specific type of packaging instead by addionally pa
 glimmer package[msi]
 ```
 
+This generates a DMG file on the Mac:
+
+```
+glimmer package[dmg]
+```
+
 Make sure to surround with double-quotes when running from ZShell (zsh):
 
 ```
-glimmer "package[msi]"
+glimmer "package[dmg]"
 ```
 
-- Available Mac packaging types are `dmg`, `pkg`, and `image` (image means a pure Mac `app` without a setup program). Keep in mind that the packages you produce are compatible with the same MacOS you are on or older.
-- Available Windows packaging types are `msi`, `exe`, and `image` (image means a Windows application directory without a setup program). Learn more about Windows packaging are [over here](#windows-application-packaging).
+- Available Mac packaging types are `dmg`, `pkg`, and `app-image` (image means a pure Mac `app` without a setup program). Keep in mind that the packages you produce are compatible with the same MacOS you are on or older.
+- Available Windows packaging types are `msi`, `exe`, and `app-image` (image means a Windows application directory without a setup program). Learn more about Windows packaging are [over here](#windows-application-packaging).
+- Available Linux packaging types are `deb`, `rpm`, and `app-image` (Note: Linux native packaging has not been tested successfully, which is why `glimmer package:gem` is recommended on Linux instead. If you get it working, please contribute to this doc file with a Pull Request).
 
 Note: if you are using Glimmer manually, to make the `glimmer package` command available, you must add the following line to your application `Rakefile` (automatically done for you if you scaffold an app or gem with `glimmer scaffold[AppName]` or `glimmer scaffold:gem:customshell[GemName]`):
 
@@ -40,20 +45,20 @@ The Glimmer packaging process done in the `glimmer package` command consists of
 1. Lock JAR versions (`glimmer package:lock_jars`): This locks versions of JAR dependencies leveraged by the `jar-dependencies` JRuby gem, downloading them into the `./vendor` directory so they would get inside the top-level Glimmer app/gem JAR file.
 1. Generate [Warbler](https://github.com/jruby/warbler) config (`glimmer package:config`): Generates initial Warbler config file (under `./config/warble.rb`) to use for generating JAR file.
 1. Generate JAR file using [Warbler](https://github.com/jruby/warbler) (`glimmer package:jar`): Enables bundling a Glimmer app into a JAR file under the `./dist` directory
-1. Generate native executable using [javapackager](https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html) (`glimmer package:native`): Enables packaging a JAR file as a DMG/PKG/APP file on Mac, MSI/EXE/APP on Windows, and DEB/RPM/APP on Linux (Glimmer does not officially support Linux with the `glimmer package` command yet, but it generates the JAR file successfully, and you could use `javapackager` manually afterwards if needed).
+1. Generate native executable using [jpackage](https://docs.oracle.com/en/java/javase/14/jpackage/packaging-tool-user-guide.pdf) (`glimmer package:native`): Enables packaging a JAR file as a DMG/PKG/APP file on Mac, MSI/EXE/APP on Windows, and DEB/RPM/APP on Linux (Glimmer does not officially support Linux with the `glimmer package` command yet, but it generates the JAR file successfully, and you could use `jpackage` manually afterwards if needed).
 
-Those steps automatically ensure generating a JAR file under the `./dist` directory using [Warbler](https://github.com/jruby/warbler), which is then used to automatically generate a DMG/MSI file (and other executables) under the `./packages/bundles` directory using `javapackager`.
+Those steps automatically ensure generating a JAR file under the `./dist` directory using [Warbler](https://github.com/jruby/warbler), which is then used to automatically generate a DMG/MSI file (and other executables) under the `./packages/bundles` directory using `jpackage`.
 The JAR file name will match your application local directory name (e.g. `MathBowling.jar` for `~/code/MathBowling`)
 The DMG file name will match the humanized local directory name + dash + application version (e.g. `Math Bowling-1.0.dmg` for `~/code/MathBowling` with version 1.0 or unspecified)
 
 The `glimmer package` command will automatically set "mac.CFBundleIdentifier" to ="org.#{project_name}.application.#{project_name}".
-You may override by configuring as an extra argument for javapackger (e.g. Glimmer::RakeTask::Package.javapackager_extra_args = " -Bmac.CFBundleIdentifier=org.andymaleh.application.MathBowling")
+You may override by configuring as an extra argument for javapackger (e.g. Glimmer::RakeTask::Package.jpackage_extra_args = " --mac-package-identifier org.andymaleh.application.MathBowling")
 
 ### Packaging Defaults
 
 Glimmer employs smart defaults in packaging.
 
-The package application name (shows up in top menu bar on the Mac) will be a human form of the app root directory name (e.g. "Math Bowling" for "MathBowling" or "math_bowling" app root directory name). However, application name and version may be specified explicitly via "-Bmac.CFBundleName" and "-Bmac.CFBundleVersion" options.
+The package application name (shows up in top menu bar on the Mac) will be a human form of the app root directory name (e.g. "Math Bowling" for "MathBowling" or "math_bowling" app root directory name). However, application name and version may be specified explicitly via "--name", "--mac-package-name" and "--version" options.
 
 Also, the package will only include these directories: app, config, db, lib, script, bin, docs, fonts, images, sounds, videos
 
@@ -74,47 +79,41 @@ require_relative '../app/my_application.rb'
 - Include Icon (Optional): If you'd like to include an icon for your app (.icns format on the Mac), place it under `package/macosx` matching the humanized application local directory name (e.g. 'Math Bowling.icns' [containing space] for MathBowling or math_bowling). You may generate your Mac icon easily using tools like Image2Icon (http://www.img2icnsapp.com/) or manually using the Mac terminal command `iconutil` (iconutil guide: https://applehelpwriter.com/tag/iconutil/)
 - Include DMG Background Icon (Optional): Simply place a .png file under `package/macosx/{HumanAppName}-background.png`
 - Include Version (Optional): Create a `VERSION` file in your application and fill it your app version on one line (e.g. `1.1.0`)
-- Include License (Optional): Create a `LICENSE.txt` file in your application and fill it up with your license (e.g. MIT). It will show up to people when installing your app. Note that, you may optionally also specify license type, but you'd have to do so manually via `-BlicenseType=MIT` shown in an [example below](#javapackager-extra-arguments).
-- Extra args (Optional): You may optionally add the following to `Rakefile` to configure extra arguments for javapackager: `Glimmer::RakeTask::Package.javapackager_extra_args = "..."` (Useful to avoid re-entering extra arguments on every run of rake task.). Read about them in [their section below](#javapackager-extra-arguments).
+- Include License (Optional): Create a `LICENSE.txt` file in your application and fill it up with your license (e.g. MIT). It will show up to people when installing your app. Note that, you may optionally also specify license type, but you'd have to do so manually via `--license-file LICENSE.txt` shown in an [example below](#jpackage-extra-arguments).
+- Extra args (Optional): You may optionally add the following to `Rakefile` to configure extra arguments for jpackage: `Glimmer::RakeTask::Package.jpackage_extra_args = "..."` (Useful to avoid re-entering extra arguments on every run of rake task.). Read about them in [their section below](#jpackage-extra-arguments).
 
-### javapackager Extra Arguments
+### jpackage Extra Arguments
 
-(note: currently `Glimmer::RakeTask::Package.javapackager_extra_args` is only honored when packaging from bash, not zsh)
+(note: currently `Glimmer::RakeTask::Package.jpackage_extra_args` is only honored when packaging from bash, not zsh)
 
-In order to explicitly configure javapackager, Mac package attributes, or sign your Mac app to distribute on the App Store, you can follow more advanced instructions for `javapackager` here:
-- https://docs.oracle.com/javase/9/tools/javapackager.htm#JSWOR719
-- https://docs.oracle.com/javase/8/docs/technotes/tools/unix/javapackager.html
-- https://docs.oracle.com/javase/8/docs/technotes/guides/deploy/self-contained-packaging.html#BCGICFDB
-- https://docs.oracle.com/javase/8/docs/technotes/guides/deploy/self-contained-packaging.html
+In order to explicitly configure jpackage, Mac package attributes, or sign your Mac app to distribute on the App Store, you can follow more advanced instructions for `jpackage` here:
+- Run `jpackage --help` for more info
+- https://docs.oracle.com/en/java/javase/14/jpackage/packaging-tool-user-guide.pdf
 - https://developer.apple.com/library/archive/releasenotes/General/SubmittingToMacAppStore/index.html#//apple_ref/doc/uid/TP40010572-CH16-SW8
 
-The Glimmer rake task allows passing extra options to javapackager via:
-- `Glimmer::RakeTask::Package.javapackager_extra_args="..."` in your application Rakefile
-- Environment variable: `JAVAPACKAGER_EXTRA_ARGS`
+The Glimmer rake task allows passing extra options to jpackage via:
+- `Glimmer::RakeTask::Package.jpackage_extra_args="..."` in your application Rakefile
+- Environment variable: `JPACKAGE_EXTRA_ARGS`
 
 Example (Rakefile):
 
 ```ruby
 require 'glimmer/rake_task'
 
-Glimmer::RakeTask::Package.javapackager_extra_args = '-BlicenseType="MIT" -Bmac.category="public.app-category.business" -Bmac.signing-key-developer-id-app="Andy Maleh"'
+Glimmer::RakeTask::Package.jpackage_extra_args = '--license-file LICENSE.txt --mac-sign --mac-signing-key-user-name "Andy Maleh"'
 ```
 
-Note that `mac.category` defaults to "public.app-category.business", but can be overridden with one of the category UTI values mentioned here:
-
-https://developer.apple.com/library/archive/releasenotes/General/SubmittingToMacAppStore/index.html#//apple_ref/doc/uid/TP40010572-CH16-SW8
-
 Example (env var):
 
 ```
-JAVAPACKAGER_EXTRA_ARGS='-Bmac.CFBundleName="Math Bowling Game"' glimmer package
+JPACKAGE_EXTRA_ARGS='--mac-package-name "Math Bowling Game"' glimmer package
 ```
 
 That overrides the default application display name.
 
 ### Verbose Mode
 
-Pass `-v` to javapackager in `Glimmer::RakeTask::Package.javapackager_extra_args` or by running `glimmer package:native[type] -v` to learn more about further available customizations for the installer you are requesting to generate.
+Pass `-v` to jpackage in `Glimmer::RakeTask::Package.jpackage_extra_args` or by running `glimmer package:native[type] -v` to learn more about further available customizations for the installer you are requesting to generate.
 
 ### Windows Application Packaging
 
@@ -128,83 +127,74 @@ If you just want to test out packaging into a native Windows app that is not pac
 
 Recent macOS versions (starting with Catalina) have very stringent security requirements requiring all applications to be signed before running (unless the user goes to System Preferences -> Privacy -> General tab and clicks "Open Anyway" after failing to open application the first time they run it). So, to release a desktop application on the Mac, it is recommended to enroll in the [Apple Developer Program](https://developer.apple.com/programs/) to distribute on the [Mac App Store](https://developer.apple.com/distribute/) or otherwise request [app notarization from Apple](https://developer.apple.com/documentation/xcode/notarizing_macos_software_before_distribution) to distribute independently.
 
-Afterwards, you may add developer-id/signing-key arguments to `javapackager` via `Glimmer::RakeTask::Package.javapackager_extra_args` or `JAVAPACKAGER_EXTRA_ARGS` according to this webpage: https://docs.oracle.com/javase/9/tools/javapackager.htm#JSWOR719
+Afterwards, you may add signing arguments to `jpackage` via `Glimmer::RakeTask::Package.jpackage_extra_args` or `JPACKAGE_EXTRA_ARGS` according to this webpage: https://docs.oracle.com/en/java/javase/14/jpackage/packaging-tool-user-guide.pdf
 
-DMG signing key argument:
 ```
--Bmac.signing-key-developer-id-app="..."
-```
-
-PKG signing key argument:
-```
--Bmac.signing-key-developer-id-installer="..."
-```
-
-Mac App Store signing key arguments:
-```
--Bmac.signing-key-app="..."
--Bmac.signing-key-pkg="..."
-```
-
-### Self Signed Certificate
-
-You may still release a signed DMG file without enrolling into the Apple Developer Program with the caveat that users will always fail in opening the app the first time, and have to go to System Preferences -> Privacy -> General tab to "Open Anyway".
-
-To do so, you may follow these steps (abbreviated version from https://developer.apple.com/library/archive/documentation/Security/Conceptual/CodeSigningGuide/Procedures/Procedures.html#//apple_ref/doc/uid/TP40005929-CH4-SW2):
-- Open Keychain Access
-- Choose Keychain Access > Certificate Assistant > Create Certificate ...
-- Enter Name (referred to below as "CertificateName")
-- Set 'Certificate Type' to 'Code Signing'
-- Create (if you alternatively override defaults, make sure to enable all capabilities)
-- Add the following option to javapackager: `-Bmac.signing-key-developer-id-app="CertificateName"` via `Glimmer::RakeTask::Package.javapackager_extra_args` or `JAVAPACKAGER_EXTRA_ARGS`
-
-Example:
-
-```ruby
-Glimmer::RakeTask::Package.javapackager_extra_args = '-Bmac.signing-key-developer-id-app="Andy Maleh"'
+  --mac-package-signing-prefix <prefix string>
+          When signing the application package, this value is prefixed
+          to all components that need to be signed that don't have
+          an existing package identifier.
+  --mac-sign
+          Request that the package be signed
+  --mac-signing-keychain <file path>
+          Path of the keychain to search for the signing identity
+          (absolute path or relative to the current directory).
+          If not specified, the standard keychains are used.
+  --mac-signing-key-user-name <team name>
+          Team name portion in Apple signing identities' names.
+          For example "Developer ID Application: "
 ```
 
-Now, when you run `glimmer package`, it builds a self-signed DMG file. When you make available online, and users download, upon launching application, they are presented with your certificate, which they have to sign if they trust you in order to use the application.
-
 ### Packaging Gotchas
 
-1. Specifying License File
-
-The javapackager documentation states that a license file may be specified with "-BlicenseFile" javapackager option. However, in order for that to work, one must specify as a source file via "-srcfiles" javapackager option.
-Keep that in mind if you are not going to rely on the default `LICENSE.txt` support.
-
-Example:
-
-```ruby
-Glimmer::RakeTask::Package.javapackager_extra_args = '-srcfiles "ACME.txt" -BlicenseFile="ACME.txt" -BlicenseType="ACME"'
-```
+1. Zsh (Z Shell)
 
-2. Mounted DMG Residue
+Currently, `Glimmer::RakeTask::Package.jpackage_extra_args` is only honored when packaging from bash, not zsh.
 
-If you run `glimmer package` multiple times, sometimes it leaves a mounted DMG project in your finder. Unmount before you run the command again or it might fail with an error saying: "Error: Bundler "DMG Installer" (dmg) failed to produce a bundle."
-
-By the way, keep in mind that during normal operation, it does also indicate a false-negative while completing successfully similar to the following (please ignore):
+You can get around that in zsh by running glimmer package commands with `bash -c` prefix:
 
 ```
-Exec failed with code 2 command [[/usr/bin/SetFile, -c, icnC, /var/folders/4_/g1sw__tx6mjdgyh3mky7vydc0000gp/T/fxbundler4076750801763032201/images/MathBowling/.VolumeIcon.icns] in unspecified directory
+bash -c 'source ~/.glimmer_source; glimmer package'
 ```
 
-3. Zsh (Z Shell)
-
-Currently, `Glimmer::RakeTask::Package.javapackager_extra_args` is only honored when packaging from bash, not zsh.
+2. unsupported Java version "16", defaulting to 1.7
 
-You can get around that in zsh by running glimmer package commands with `bash -c` prefix:
+If you get this error while packaging:
 
 ```
-bash -c 'source ~/.glimmer_source; glimmer package'
+unsupported Java version "16", defaulting to 1.7
+[ERROR] Internal error: org.jruby.exceptions.RaiseException: (LoadError) library `java' could not be loaded: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not "opens java.lang" to unnamed module @138caeca -> [Help 1]
+org.apache.maven.InternalErrorException: Internal error: org.jruby.exceptions.RaiseException: (LoadError) library `java' could not be loaded: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not "opens java.lang" to unnamed module @138caeca
+  at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
+  at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
+  at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
+  at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
+  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
+  at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:78)
+  at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
+  at java.base/java.lang.reflect.Method.invoke(Method.java:567)
+  at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
+  at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
+  at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
+  at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
+Caused by: org.jruby.exceptions.RaiseException: (LoadError) library `java' could not be loaded: java.lang.reflect.InaccessibleObjectException: Unable to make protected native java.lang.Object java.lang.Object.clone() throws java.lang.CloneNotSupportedException accessible: module java.base does not "opens java.lang" to unnamed module @138caeca
+[ERROR]
+[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
+[ERROR] Re-run Maven using the -X switch to enable full debug logging.
+[ERROR]
+[ERROR] For more information about the errors and possible solutions, please read the following articles:
+[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/InternalErrorException
 ```
 
-4. Java on Windows System PATH
+Please ignore. It should be harmless. If you get blocked by it for any reason, please open an Issue about it.
 
-If you get any errors running Java on Windows, keep in mind that you need to have the Java binaries on the Windows System PATH environment variable:
-c:\program files\java\jre1.8.0_241
+3. Java on Windows System PATH
+
+If you get any errors running Java on Windows, keep in mind that you need to have the Java binaries "C:\Program Files\Java\jdk-16.0.2\bin" on the Windows System PATH environment variable.
 
 The problem is Oracle seems to be adding an indirect Java path junction in later versions of their installer:
-C:\Program Files (x86)\Common Files\Oracle\Java\javapath
+`C:\Program Files (x86)\Common Files\Oracle\Java\javapath`
+
+Simply replace it with the simple path mentioned above (`"C:\Program Files\Java\jdk-16.0.2\bin"` matching your correct version number)
 
-Simply replace with the simple one above (setting the correct version number) and then reinstall JRuby to have it use Java from the right path.
+Lastly, reinstall JRuby to ensure it is using Java from the right path.

data/lib/glimmer/launcher.rb

@@ -146,7 +146,7 @@ module Glimmer
       end
     end
     
-    attr_reader :application_path
+    attr_reader :application_paths
     attr_reader :env_vars
     attr_reader :glimmer_options
     attr_reader :jruby_options

data/lib/glimmer/rake_task/package.rb

@@ -26,8 +26,7 @@ module Glimmer
   module RakeTask
     module Package
       class << self
-        attr_accessor :javapackager_extra_args
-        alias jpackage_extra_args javapackager_extra_args
+        attr_accessor :jpackage_extra_args
         
         def clean
           require 'fileutils'
@@ -89,12 +88,12 @@ module Glimmer
         end
         
         def native(native_type=nil, native_extra_args)
-          puts "Generating native executable with javapackager/jpackage..."
+          puts "Generating native executable with jpackage..."
           java_version = `jruby -v`
-          if java_version.include?('1.8.0_241')
-            puts "Java Version 1.8.0_241 Detected!"
+          if java_version.include?('16.0.2')
+            puts "Java Version 16.0.2 Detected!"
           else
-            puts "WARNING! Glimmer Packaging Pre-Requisite Java Version 1.8.0_241 Is Not Found!"
+            puts "WARNING! Glimmer Packaging Pre-Requisite Java Version 16.0.2 Is Not Found!"
           end
           require 'facets/string/titlecase'
           require 'facets/string/underscore'
@@ -106,28 +105,27 @@ module Glimmer
           license = (File.read(license_file).strip if File.exists?(license_file) && File.file?(license_file)) rescue nil
           copyright = license.split("\n").first
           human_name = project_name.underscore.titlecase
-          icon = "package/#{OS.mac? ? 'macosx' : 'windows'}/#{human_name}.#{OS.mac? ? 'icns' : 'ico'}"
-          if (`javapackager`.to_s.include?('Usage: javapackager') rescue nil)
-            command = "javapackager -deploy -native #{native_type} -outdir packages -outfile \"#{project_name}\" -srcfiles \"dist/#{project_name}.jar\" -appclass JarMain -name \"#{human_name}\" -title \"#{human_name}\" -Bmac.CFBundleName=\"#{human_name}\" -Bmac.CFBundleIdentifier=\"org.#{project_name}.application.#{project_name.camelcase(:upper)}\" -Bmac.category=\"public.app-category.business\" -BinstalldirChooser=true -Bvendor=\"#{human_name}\" -Bwin.menuGroup=\"#{human_name}\" "
-            command += " -BsystemWide=false " if OS.windows?
-            command += " -BjvmOptions=-XstartOnFirstThread " if OS.mac?
-            command += " -BappVersion=#{version} -Bmac.CFBundleVersion=#{version} " if version
-            command += " -srcfiles LICENSE.txt -BlicenseFile=LICENSE.txt " if license
-            command += " -Bcopyright=\"#{copyright}\" " if copyright
-          elsif (`jpackage`.to_s.include?('Usage: jpackage') rescue nil)
-            command = "jpackage --type #{native_type} --dest 'packages/bundles' --input 'dist' --main-class JarMain --main-jar '#{project_name}.jar' --name '#{human_name}' --vendor '#{human_name}' --icon '#{icon}' "
-            command += " --win-per-user-install --win-dir-chooser --win-menu --win-menu-group '#{human_name}' " if OS.windows?
+          icon = "icons/#{OS.mac? ? 'macosx' : (OS.linux? ? 'linux' : 'windows')}/#{human_name}.#{OS.mac? ? 'icns' : (OS.linux? ? 'png' : 'ico')}"
+          native_type = 'app-image' if native_type.to_s.strip.empty?
+          if (`jpackage`.to_s.include?('Usage: jpackage') rescue nil)
+            FileUtils.rm_rf("packages/bundles")
+            FileUtils.mkdir_p('packages/bundles')
+            command = "jpackage"
+            command += " --type #{native_type}"
+            command += " --dest 'packages/bundles' --input 'dist' --main-class JarMain --main-jar '#{project_name}.jar' --java-options '-Dproject_name=#{project_name}' --name '#{human_name}' --vendor '#{human_name}' --icon '#{icon}' "
+            command += " --win-per-user-install --win-dir-chooser --win-menu --win-menu-group '#{human_name}' " if OS.windows? && native_type != 'app-image'
+            command += " --linux-menu-group '#{human_name}' " if OS.linux? && native_type != 'app-image'
             command += " --java-options '-XstartOnFirstThread' --mac-package-name '#{human_name}' --mac-package-identifier 'org.#{project_name}.application.#{project_name}' " if OS.mac?
             command += " --app-version \"#{version}\" " if version
-            command += " --license-file LICENSE.txt " if license
+            command += " --license-file LICENSE.txt " if license && native_type != 'app-image'
             command += " --copyright \"#{copyright}\" " if copyright
           else
-            puts "Neither javapackager nor jpackage exist in your Java installation. Please ensure javapackager or jpackage is available in PATH environment variable."
+            puts "jpackage does not exist in your Java installation. Please ensure jpackage is available in PATH environment variable."
             return
           end
-          Rake.application.load_rakefile # make sure to load potential javapackager_extra_args config in app Rakefile
-          command += " #{javapackager_extra_args} " if javapackager_extra_args
-          command += " #{ENV['JAVAPACKAGER_EXTRA_ARGS']} " if ENV['JAVAPACKAGER_EXTRA_ARGS']
+          Rake.application.load_rakefile # make sure to load potential jpackage_extra_args config in app Rakefile
+          command += " #{jpackage_extra_args} " if jpackage_extra_args
+          command += " #{ENV['JPACKAGE_EXTRA_ARGS']} " if ENV['JPACKAGE_EXTRA_ARGS']
           command += " #{native_extra_args} " if native_extra_args
           puts command
           system command

data/lib/glimmer/rake_task/scaffold.rb

@@ -167,20 +167,25 @@ module Glimmer
             custom_shell('AppView', current_dir_name, shell_type)
           end
             
-          mkdir_p 'package/windows'
-          icon_file = "package/windows/#{human_name(app_name)}.ico"
+          mkdir_p 'icons/windows'
+          icon_file = "icons/windows/#{human_name(app_name)}.ico"
           cp File.expand_path('../../../../icons/scaffold_app.ico', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
           
-          mkdir_p 'package/macosx'
-          icon_file = "package/macosx/#{human_name(app_name)}.icns"
+          mkdir_p 'icons/macosx'
+          icon_file = "icons/macosx/#{human_name(app_name)}.icns"
           cp File.expand_path('../../../../icons/scaffold_app.icns', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
         
-          mkdir_p 'package/linux'
-          icon_file = "package/linux/#{human_name(app_name)}.png"
+          mkdir_p 'icons/linux'
+          icon_file = "icons/linux/#{human_name(app_name)}.png"
           cp File.expand_path('../../../../icons/scaffold_app.png', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
+          
+          write "Resource.java", resource_java_file(app_name)
+          cd '..'
+          system "javac #{file_name(app_name)}/Resource.java"
+          cd gem_name
         
           mkdir_p "app/#{file_name(app_name)}"
           write "app/#{file_name(app_name)}/launch.rb", app_launch_file(app_name)
@@ -195,14 +200,14 @@ module Glimmer
           end
           write 'spec/spec_helper.rb', spec_helper_file
           if OS.windows?
-            system "glimmer \"package[image]\"" # TODO handle Windows with batch file
+            system "glimmer package" # TODO handle Windows with batch file
             system "\"packages/bundles/#{human_name(app_name)}/#{human_name(app_name)}.exe\""
           else
             system "bash -c '#{RVM_FUNCTION}\n cd .\n glimmer package\n'"
             if OS.mac?
-              system "open packages/bundles/#{human_name(app_name).gsub(' ', '\ ')}.app"
+              system "bash -c '#{RVM_FUNCTION}\n cd .\n JRUBY_OPTS=\"$JRUBY_OPTS -J-XstartOnFirstThread\" glimmer run\n'"
             else
-              system "glimmer run"
+              system "bash -c '#{RVM_FUNCTION}\n cd .\n glimmer run\n'"
             end
           end
         end
@@ -278,30 +283,35 @@ module Glimmer
           end
           write 'spec/spec_helper.rb', spec_helper_file
     
-          mkdir_p 'package/windows'
-          icon_file = "package/windows/#{human_name(custom_shell_name)}.ico"
+          mkdir_p 'icons/windows'
+          icon_file = "icons/windows/#{human_name(custom_shell_name)}.ico"
           cp File.expand_path('../../../../icons/scaffold_app.ico', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
             
-          mkdir_p 'package/macosx'
-          icon_file = "package/macosx/#{human_name(custom_shell_name)}.icns"
+          mkdir_p 'icons/macosx'
+          icon_file = "icons/macosx/#{human_name(custom_shell_name)}.icns"
           cp File.expand_path('../../../../icons/scaffold_app.icns', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
           
-          mkdir_p 'package/linux'
-          icon_file = "package/linux/#{human_name(custom_shell_name)}.png"
+          mkdir_p 'icons/linux'
+          icon_file = "icons/linux/#{human_name(custom_shell_name)}.png"
           cp File.expand_path('../../../../icons/scaffold_app.png', __FILE__), icon_file
           puts "Created #{current_dir_name}/#{icon_file}"
           
+          write "Resource.java", resource_java_file(custom_shell_name)
+          cd '..'
+          system "javac #{file_name(custom_shell_name)}/Resource.java"
+          cd gem_name
+          
           if OS.windows?
-            system "glimmer package[image]" # TODO handle windows properly with batch file
+            system "glimmer package" # TODO handle windows properly with batch file
             system "\"packages/bundles/#{human_name(custom_shell_name)}/#{human_name(custom_shell_name)}.exe\""
           else
             system "bash -c '#{RVM_FUNCTION}\n cd .\n glimmer package\n'"
             if OS.mac?
-              system "open packages/bundles/#{human_name(custom_shell_name).gsub(' ', '\ ')}.app"
+              system "bash -c '#{RVM_FUNCTION}\n cd .\n JRUBY_OPTS=\"$JRUBY_OPTS -J-XstartOnFirstThread\" glimmer run\n'"
             else
-              system "glimmer run"
+              system "bash -c '#{RVM_FUNCTION}\n cd .\n glimmer run\n'"
             end
           end
           puts "Finished creating #{gem_name} Ruby gem."
@@ -485,6 +495,16 @@ module Glimmer
             #{class_name(app_name)}::View::AppView.launch
           MULTI_LINE_STRING
         end
+        
+        def resource_java_file(app_name)
+          <<~MULTI_LINE_STRING
+            package #{file_name(app_name)};
+            
+            /** The soul purpose of this class is to retrieve icons for uri:classloader paths used from JAR */
+            class Resource {
+            }
+          MULTI_LINE_STRING
+        end
     
         def app_bin_command_file(app_name_or_gem_name, custom_shell_name=nil, namespace=nil)
           if custom_shell_name.nil?
@@ -525,7 +545,7 @@ module Glimmer
           lines.insert(require_rake_line_index, "require 'glimmer/launcher'")
           gem_files_line_index = lines.index(lines.detect {|l| l.include?('# dependencies defined in Gemfile') })
           if custom_shell_name
-            lines.insert(gem_files_line_index, "  gem.files = Dir['VERSION', 'LICENSE.txt', 'app/**/*', 'bin/**/*', 'config/**/*', 'db/**/*', 'docs/**/*', 'fonts/**/*', 'icons/**/*', 'images/**/*', 'lib/**/*', 'package/**/*', 'script/**/*', 'sounds/**/*', 'vendor/**/*', 'videos/**/*']")
+            lines.insert(gem_files_line_index, "  gem.files = Dir['Resource.class', 'VERSION', 'LICENSE.txt', 'app/**/*', 'bin/**/*', 'config/**/*', 'db/**/*', 'docs/**/*', 'fonts/**/*', 'icons/**/*', 'images/**/*', 'lib/**/*', 'script/**/*', 'sounds/**/*', 'vendor/**/*', 'videos/**/*']")
             # the second executable is needed for warbler as it matches the gem name, which is the default expected file (alternatively in the future, we could do away with it and configure warbler to use the other file)
             lines.insert(gem_files_line_index+1, "  gem.require_paths = ['vendor', 'lib', 'app']")
             lines.insert(gem_files_line_index+2, "  gem.executables = ['#{file_name(custom_shell_name)}']") if custom_shell_name
@@ -538,14 +558,10 @@ module Glimmer
           file_content = lines.join("\n")
           if custom_shell_name
             file_content << <<~MULTI_LINE_STRING
-              Glimmer::RakeTask::Package.javapackager_extra_args =
-                " -name '#{human_name(custom_shell_name)}'" +
-                " -title '#{human_name(custom_shell_name)}'" +
-                " -Bmac.CFBundleName='#{human_name(custom_shell_name)}'" +
-                " -Bmac.CFBundleIdentifier='org.#{namespace ? compact_name(namespace) : compact_name(custom_shell_name)}.application.#{compact_name(custom_shell_name).camelcase(:upper)}'"
-                # " -BlicenseType=" +
-                # " -Bmac.category=" +
-                # " -Bmac.signing-key-developer-id-app="
+              Glimmer::RakeTask::Package.jpackage_extra_args =
+                " --name '#{human_name(custom_shell_name)}'" +
+                " --description '#{human_name(custom_shell_name)}'"
+                # You can add more options from https://docs.oracle.com/en/java/javase/14/jpackage/packaging-tool-user-guide.pdf
             MULTI_LINE_STRING
           end
           file_content
@@ -643,7 +659,8 @@ module Glimmer
         shell#{'(:fill_screen)' if shell_type == :desktopify} {
           # Replace example content below with custom shell content
           minimum_size #{shell_type == :desktopify ? '768, 432' : '420, 240'}
-          image File.join(APP_ROOT, 'package', 'windows', "#{human_name(shell_type == :gem ? custom_shell_name : current_dir_name)}.ico") if OS.windows?
+          image File.join(APP_ROOT, 'icons', 'windows', "#{human_name(shell_type == :gem ? custom_shell_name : current_dir_name)}.ico") if OS.windows?
+          image File.join(APP_ROOT, 'icons', 'linux', "#{human_name(shell_type == :gem ? custom_shell_name : current_dir_name)}.png") unless OS.windows?
           text "#{human_name(namespace)} - #{human_name(custom_shell_name)}"
         
           MULTI_LINE_STRING

data/lib/glimmer/swt/image_proxy.rb

@@ -122,9 +122,9 @@ module Glimmer
       def input_stream
         if @file_path.start_with?('uri:classloader')
           @jar_file_path = @file_path
-          file_path = @jar_file_path.sub(/^uri\:classloader\:/, '').sub('//', '/') # the latter sub is needed for Mac
-          object = java.lang.Object.new
-          file_input_stream = object.java_class.resource_as_stream(file_path)
+          file_path = @jar_file_path.sub(/^uri\:classloader\:/, '').sub('//', '') # the latter sub is needed for Mac
+          project_name = java.lang.System.getProperty('project_name')
+          file_input_stream = java_import("#{project_name}.Resource").last.java_class.resource_as_stream(file_path)
         else
           file_input_stream = java.io.FileInputStream.new(@file_path)
         end

metadata

@@ -1,14 +1,14 @@
 --- !ruby/object:Gem::Specification
 name: glimmer-dsl-swt
 version: !ruby/object:Gem::Version
-  version: 4.20.16.0
+  version: 4.21.0.0
 platform: ruby
 authors:
 - Andy Maleh
 autorequire:
 bindir: bin
 cert_chain: []
-date: 2021-12-10 00:00:00.000000000 Z
+date: 2021-09-27 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
@@ -238,6 +238,20 @@ dependencies:
     - - "<"
       - !ruby/object:Gem::Version
         version: 4.0.0
+- !ruby/object:Gem::Dependency
+  requirement: !ruby/object:Gem::Requirement
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 3.3.2
+  name: psych
+  prerelease: false
+  type: :runtime
+  version_requirements: !ruby/object:Gem::Requirement
+    requirements:
+    - - '='
+      - !ruby/object:Gem::Version
+        version: 3.3.2
 - !ruby/object:Gem::Dependency
   requirement: !ruby/object:Gem::Requirement
     requirements:
@@ -712,7 +726,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
     - !ruby/object:Gem::Version
       version: '0'
 requirements: []
-rubygems_version: 3.1.6
+rubygems_version: 3.2.14
 signing_key:
 specification_version: 4
 summary: Glimmer DSL for SWT (JRuby Desktop Development GUI Framework)