making java depency user suppliable or optional

[gseac]

We have a wrapper cookbook around the "bamboo" cookbook. the cookbook defines a dependency on Java. We have our own internal Java cookbook which installs Java slightly differently and also perform some other custom actions. Would would be amenable to making the Java dependency something optional. Optional, in the sense the user would need to supply that dependency.

Regards,

[ramonskie]

can i ask more about your usecase?
what are you exactly doing with the specialized java?
is it specific change for bamboo?

[gseac]

We support multiple versions of Java, so our java_home varies with applications. We also install some SSL certificates as part of our java install. We like the functionality provided by the bamboo cookbook we just would like to had it skip the java install.

[ramonskie]

well we also do this with a wrapper cookbook
the only thing you need to do is let your adjusted java cookbook install on a different location
so that the bamboo agent/server uses the cookbook we provided here.

and for the bamboo build we use different java versions