AndyObtiva
commented
2 years ago Interesting.
I tested scaffolding successfully with v4.24.1.0 when I released it on July 22, 2022. In fact, I still have the scaffolded app on my machine, and I was able to run glimmer run from it just fine.
I just scaffolded a new app with v4.24.1.0, and I got the error you mentioned:
LoadError: no such file to load -- rspec/core
This seems to be caused by some prerequisite gems getting updated, and breaking the expectations of the glimmer-dsl-swt gem somehow. jar-dependencies 0.4.2 definitely seems like an offender. I wonder if there is a bug with the gem. I couldn't know for sure without spending more time digging into the problem.
The outcome of this is that scaffolding got interrupted, so development-related functionality is not fully scaffolded. However, the application code is fully scaffolded.
One workaroud for running the app that worked for me is to follow these steps:
1) Edit Gemfile and disable all :development gems except warbler, and then run bundle. That will get rid of the jar-dependencies gem dependency. The file should look like this at the end:
# frozen_string_literal: true
source 'https://rubygems.org'
git_source(:github) {|repo_name| "https://github.com/#{repo_name}" }
gem 'glimmer-dsl-swt', '~> 4.24.1.0'
group :development do
# gem 'rspec', '~> 3.5.0'
# gem 'juwelier', '2.4.9'
gem 'warbler', '2.0.5'
# gem 'simplecov', '>= 0'
end2) Disable juwelier, rspec and simplecov related code in Rakefile. Your Rakefile should end up looking like this:
# encoding: utf-8
require 'rubygems'
require 'bundler'
begin
Bundler.setup(:default, :development)
rescue Bundler::BundlerError => e
$stderr.puts e.message
$stderr.puts "Run `bundle install` to install missing gems"
exit e.status_code
end
require 'glimmer/launcher'
require 'rake'
# require 'juwelier'
# Juwelier::Tasks.new do |gem|
# # gem is a Gem::Specification... see http://guides.rubygems.org/specification-reference/ for more options
# gem.name = "snowboard_utah"
# gem.homepage = "http://github.com/AndyObtiva/snowboard_utah"
# gem.license = "MIT"
# gem.summary = %Q{Snowboard Utah}
# gem.description = %Q{Snowboard Utah}
# gem.email = "andy.am@gmail.com"
# gem.authors = ["Andy Maleh"]
#
# gem.files = Dir['VERSION', 'LICENSE.txt', 'app/**/*', 'bin/**/*', 'config/**/*', 'db/**/*', 'docs/**/*', 'fonts/**/*', 'icons/**/*', 'images/**/*', 'lib/**/*', 'script/**/*', 'sounds/**/*', 'vendor/**/*', 'videos/**/*']
# gem.require_paths = ['vendor', 'lib', 'app']
# gem.executables = ['snowboard_utah']
# # dependencies defined in Gemfile
# end
# Juwelier::RubygemsDotOrgTasks.new
# require 'rspec/core'
# require 'rspec/core/rake_task'
# RSpec::Core::RakeTask.new(:spec) do |spec|
# spec.pattern = FileList['spec/**/*_spec.rb']
# spec.ruby_opts = [Glimmer::Launcher.jruby_os_specific_options]
# end
#
# desc "Code coverage detail"
# task :simplecov do
# ENV['COVERAGE'] = "true"
# Rake::Task['spec'].execute
# end
#
# task :default => :spec
#
# require 'rdoc/task'
# Rake::RDocTask.new do |rdoc|
# version = File.exist?('VERSION') ? File.read('VERSION') : ""
#
# rdoc.rdoc_dir = 'rdoc'
# rdoc.title = "snowboard_utah #{version}"
# rdoc.rdoc_files.include('README*')
# rdoc.rdoc_files.include('lib/**/*.rb')
# end
require 'glimmer/rake_task'
Glimmer::RakeTask::Package.jpackage_extra_args =
" --name 'Snowboard Utah'" +
" --description 'Snowboard Utah'"
# You can add more options from https://docs.oracle.com/en/java/javase/16/jpackage/packaging-tool-user-guide.pdf3) Run the app via either glimmer run or the scaffolded bin/app_name script. For example, if I run either glimmer run or bin/snowboard_utah (name of my app), I get this screen.
This keeps packaging functionality intact!
For example, I was able to run:
glimmer "package[dmg]"
I'm keeping this issue open till it is properly resolved, but you have a workaround in the meantime to avoid being stuck.
jayczech23
Desktop (please complete the following information and make sure it matches Glimmer Pre-Requisites before reporting an issue):
x86_64
MacOS 12.4
JDK 16.0.2
jruby 9.3.6.0
4.24.1.0
Describe the issue I am having an issue when trying to execute the newly created app from
glimmer scaffoldcommand. However, I did notice an error that occurred during the end phase ofglimmer scaffold. I am not sure if this has anything to do with the proceeding error. Please see error at gist below:Error running scaffold
Ignoring the above error, I then attempted to run newly scaffolded app as-is with
glimmer run, and receive the following error upon doing so:Error on glimmer run
Where could the issue be? Could it be with the environment?