[chef] Re: java::oracle recipe broken due to oracle now requiring browser cookie


Chronological Thread 
  • From: Zuhaib Siddique < >
  • To:
  • Cc:
  • Subject: [chef] Re: java::oracle recipe broken due to oracle now requiring browser cookie
  • Date: Wed, 28 Mar 2012 19:53:04 -0700

I actually wrote a hack Java cookbook around that script and we use that now to install Java in to our prebuilt AMI's.  I found the Opscode Java caused problems with Tomcat installed with apt-get as it did not see Sun Java and would force install OpenJDK.

 The problem with /oab-java6  it is that it takes a crap long time to package so that is why we use prebuilt AMI's that install Java another things we use.  Personally I am thinking of deploying our own repository and just host Java internally till we cut over to OpenJDK.  Most of the Engineering team I work with still does not think OpenJDK is fully baked tho I have tested our code to work on it as a pure DemVal.

I just build a new AMI today and found its still working, and I am using a fork of that project because I wanted to control any updates to it.  Maybe its only JDK7 they added this requirement because JDK6 is fine.

Zuhaib
On Mar 27, 2012, at 12:03 PM, John E. Vincent (lusis) < "> > wrote:

On Tue, Mar 27, 2012 at 2:44 PM, Adam Jacob < "> > wrote:
Seems like a great reason to move to OpenJDK. My instinct would be that if they are going to this kind of length to get you to register/use a cookie, honor their request - by downloading it locally and fetching it repeatably from a local location. Or by moving to OpenJDK. 

Adam 

Sadly OpenJDK doesn't play nice still with many applications.

Bryan,

Are you entirely positive about this? I just built two new base images a few days ago with https://github.com/flexiondotorg/oab-java6 and it worked fine. It's just a shell script.

Might be worth looking in there for inspiration. 

 




Archive powered by MHonArc 2.6.16.

§