Adoptable Cookbooks List

Looking for a cookbook to adopt? You can now see a list of cookbooks available for adoption!
List of Adoptable Cookbooks

Supermarket Belongs to the Community

Supermarket belongs to the community. While Chef has the responsibility to keep it running and be stewards of its functionality, what it does and how it works is driven by the community. The chef/supermarket repository will continue to be where development of the Supermarket application takes place. Come be part of shaping the direction of Supermarket by opening issues and pull requests or by joining us on the Chef Mailing List.

Select Badges

Select Supported Platforms

Select Status


java_wrapper (15) Versions 0.1.0

Library cookbook that exposes the java_wrapper LWRP for Installing / Configuring java_wrapper on a server.

cookbook 'java_wrapper', '= 0.1.0', :supermarket
cookbook 'java_wrapper', '= 0.1.0'
knife supermarket install java_wrapper
knife supermarket download java_wrapper
Quality -%

java_wrapper Cookbook


This cookbook provides java_wrapper, a resource that wrap a java application
to be easily managed using start up scripts. It uses


This cookbook has only be tested on linux system. Tanuki java wrapper works on
Windows system, but considering this cookbook has never been tested on Windows,
it most likely not work.

Attribute Parameters

Customize the attributes to suit your need, the following attributes
have to be provided:

  • app_name: the name of the application, if not provided, it uses the name of the resource.
  • classpath: the classpath of the application
  • app_parameters: the array of String that will be passed to the application
  • java_parameters: The array of java parameters

This attributes can be used to further customize the application:
- app_long_name: the long name use for the daemon
- app_dir: the directory in which the application is deployed, it defaults to /opt/#{app_name}
- bin_dir: the bin directory for the wrapper, it defaults to #{app_dir}/bin
- lib_idr: the lib directory for the wrapper, it defaults to #{app_dir}/lib
- conf_dir: the conf directory for the wrapper, it defaults to #{app_dir}/conf
- logs_dir: the log directory for the wrapper, it defaults to /var/log/#{name}
- init_mem_MB: the mininum memory in MB for the JVM, defaults to 3
- max_mem_MB: the maximum memory in MB for the JVM, defaults to 64
- run_as_user: the user running the wrapper, defaults to root
- wrapper_version: the version of the java wrapper, defaults to 3.5.21
- wrapper_os: the os for the java wrapper, defaults to linux
- wrapper_cpu: the cpu for the java wrapper, defaults to x86
- wrapper_bit: the architecture for the java wrapper, defaults to 64
- wrapper_extension: the extension for the java wrapper, defaults to tar.gz
- wrapper_url: the url to download the wrapper, defaults to "{wrapper_version}/wrapper-#{wrapper_os}-#{wrapper_cpu}-#{wrapper_bit}-#{wrapper_version}.#{wrapper_extension}"


You will find usage in the test recipe at

java_wrapper 'jetty' do
app_parameters ["org.mortbay.start.Main"]
classpath ["/usr/local/jetty/start.jar"]
java_parameters ["-Djetty.home=/usr/local/jetty"]

java_wrapper 'play' do
classpath ["#{helloworld_dir}/target/staged/*"]
app_parameters ["play.core.server.NettyServer", "#{helloworld_dir}"]
java_parameters ["-Dhttp.port=9001"]


  1. Fork the repository on Github
  2. Create a named feature branch (like add_component_x)
  3. Write you change
  4. Write tests for your change (if applicable)
  5. Run the tests, ensuring they all pass
  6. Submit a Pull Request using Github

License and Authors

Authors: Alexandre Russel

Dependent cookbooks

This cookbook has no specified dependencies.

Contingent cookbooks

There are no cookbooks that are contingent upon this one.

No quality metric results found