- From: Chad Woolley <
- To: Joshua Timberman <
- Cc: Adam Jacob <
>, Chef Dev <
- Subject: [[chef-dev]] Re: [[chef-dev]] Re: JAVA_HOME, sun vs. openjdk inconsistencies
- Date: Tue, 22 Jun 2010 23:37:25 -0700
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=Mg8QjO5y000r/28eJcN1Knx2nvwBbE1PVEDdykB3E1HYNEHXzD9GHzfztGpXBhKZzN 72dskNCk4gZYeiT20snQOs5aPZx9ugYS/Xtw2qYmcLOIlf3POZSFvzw5Sz/+/z7Ln7hW zXr9JiOiskqJt6qY1RdADyK7kCCC20OG+iDmw=
On Tue, Jun 1, 2010 at 4:00 PM, Joshua Timberman
> Hi Chad!
> I made the change to openjdk because the Sun java package is considered
> deprecated (though still available) in both Debian and Ubuntu. To support
> installing Sun's package where it is available, we should utilize either a
> separate recipe in the kava cookbook, or control the preferred package via
> an attribute. The default should be openjdk, as it's the default on all of
> Devian, Ubuntu and RHEL/Centos.
> Please open a ticket in the cookbook project. If you have a patch, please
> link to the github branch.
Pull request sent
). I made a
separate cookbook, java_sun. This seemed cleaner than grafting it
back into the main java cookbook as a separate recipe, especially
since I didn't know what to do with 'supports os' in metadata.rb if a
single recipe only supports certain platforms...
Archive powered by MHonArc 2.6.16.