You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Testing reveals that neither the jdk, nor the tomcat packages are dragging in the java installation, but that java package comes in as a dependency once I enable the jenkins class invocation.
Any ideas what I might be doing wrong here? Is this an issue of install_java => false failing to do what I would expect such an attribute to do for me?
Any insight would be appreciated.
-- Hugh
The text was updated successfully, but these errors were encountered:
Sorry to have ignored you. Yes, I believe you are correct here. We discussed your theory back and forth for a few days, then got interrupted by the holiday schedule. A coworker finally rebuilt that rpm locally, and this time it includes only the .war file (or at least very little else), permitting us to drop the .war into tomcat and restart the jvm and have it work. Thank you for your insight on this.
This has frustrated my work today:
results in:
vagrant@jenkins:~> rpm -qa | grep jdk
jdk-1.7.0_67-fcs
vagrant@jenkins:~> rpm -qa | grep tomcat
apache-tomcat-7.0-65
vagrant@jenkins:~> rpm -qa | grep java
java-1_6_0-ibm-1.6.0_sr16.4-0.3.1
Testing reveals that neither the jdk, nor the tomcat packages are dragging in the java installation, but that java package comes in as a dependency once I enable the jenkins class invocation.
Any ideas what I might be doing wrong here? Is this an issue of
install_java => false
failing to do what I would expect such an attribute to do for me?Any insight would be appreciated.
-- Hugh
The text was updated successfully, but these errors were encountered: