You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be really nice to have some notion of environments. My understanding is that Jars::Installer.new.vendor_jars! looks at anything in Gem::Specification requirements and installs them into the ENV['JARS_HOME'] directory.
I currently require jars for test that I do not want to bloat my runtime-jars with. Not sure what the best way to distinguish runtime jars from test jars would be, but it would be a nice feature. Maybe add en ENV=<custom_value> that could also be ready by Jars::Installer.new.vendor_jars!
Gem::Specification.new do |s|
s.requirements << "jar 'com.zaxxer:HikariCP', '2.7.2'"
s.requirements << "ENV=test jar 'org.postgresql:postgresql', '42.2.5'"
end
Above I only need HikariCP at runtime but to test I need some JDBC implementation JAR (postgres)
The text was updated successfully, but these errors were encountered:
It would be really nice to have some notion of environments. My understanding is that
Jars::Installer.new.vendor_jars!
looks at anything in Gem::Specification requirements and installs them into theENV['JARS_HOME']
directory.I currently require jars for test that I do not want to bloat my
runtime-jars
with. Not sure what the best way to distinguish runtime jars from test jars would be, but it would be a nice feature. Maybe add en ENV=<custom_value> that could also be ready byJars::Installer.new.vendor_jars!
Above I only need HikariCP at runtime but to test I need some JDBC implementation JAR (postgres)
The text was updated successfully, but these errors were encountered: