Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: test-jars #72

Open
spencerdcarlson opened this issue Jun 23, 2019 · 0 comments
Open

Feature Request: test-jars #72

spencerdcarlson opened this issue Jun 23, 2019 · 0 comments

Comments

@spencerdcarlson
Copy link

spencerdcarlson commented Jun 23, 2019

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)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant