search for: java_version

...deletion(-) diff --git a/m4/guestfs_java.m4 b/m4/guestfs_java.m4 index f9bec94..649e21f 100644 --- a/m4/guestfs_java.m4 +++ b/m4/guestfs_java.m4 @@ -84,7 +84,7 @@ if test "x$with_java" != "xno"; then else JAR="$JAVA/bin/jar" fi - java_version=`$JAVA_EXE -version 2>&1 | grep "java version"` + java_version=`$JAVA_EXE -version 2>&1 | $AWK -F '"' '/^(java|openjdk) version/ {print $2;}'` AC_MSG_RESULT(found $java_version in $JAVA) dnl Find jni.h. -- 2.5.0

...ULT([found]) JAVA=$d break + else + AC_MSG_RESULT([not found]) fi done fi @@ -85,7 +89,7 @@ if test "x$with_java" != "xno"; then JAR="$JAVA/bin/jar" fi java_version=`$JAVA_EXE -version 2>&1 | $AWK -F '"' '/^(java|openjdk) version/ {print $2;}'` - AC_MSG_RESULT(found $java_version in $JAVA) + AC_MSG_RESULT(found $java_version) dnl Find jni.h. AC_MSG_CHECKING([for jni.h]) -- 2.13.4

Add sort of "headers" to split most of the logical sections of the configure, so it is easier to get feedback on the progress of configure. --- configure.ac | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/configure.ac b/configure.ac index 7f9c1dac0..5ccf6f821 100644 --- a/configure.ac +++ b/configure.ac @@ -76,11 +76,15 @@

...bove module to work, even when the correct version isn''t configured. The next step in my mind would be to coax puppet into running sudo alternatives --set java /usr/java/jre1.6.0_45/bin/java if the installation check succeeds, but the default isn''t correctly set. I grabbed a *java_version* fact from another groups discussion<https://groups.google.com/forum/#!topic/puppet-users/W67dvqS-GdU>, and naively the module code would look something like this # if version check in package resource succeeds .. if($java_version != ''1.6.0_45'') # run sudo alternatives --...

...age, $status = $elasticsearch::params::status, $java_install = $elasticsearch::params::java_install, $java_path = $elasticsearch::params::java_path, $java_install_directory = ''UNSET'', $java_wget_url = ''UNSET'', $java_version = ''UNSET'' ) inherits elasticsearch::params{ if ! ($status in [ ''enabled'', ''disabled'', ''running'', ''unmanaged'']) { fail("status non reconnu") } # package(s) class { ''...

Here''s one for you! We''re rolling out some zip files to our servers using Puppet, there''s an exec that unzips them, the zip file is then deleted. I need to remove the old versions of the unzipped directory using Puppet when we rol out a newer version. So, on my client/node machine I have the below directories. /opt/1234 /opt/12345 /opt/123456 What I need to do, is

...worked and I now have the help.start() search engine working in the 2002-11-22 Mozilla 1.3a build. The note would suggest that the browser may have problems locating the required Java modules to load and start the applet. The fix seems to be to create (as root) a symlink to the file: /usr/java/JAVA_VERSION/plugin/i386/ns610/libjavaplugin_oji.so in your active Mozilla plugins directory. In the process of doing this, I noted that there were multiple Moz* directories in /usr/lib, given the updating that I have done since installing RH 8.0. There was no symlink in usr/lib/Mozilla-1.3a/plugins. Upon...

Hello all, I am currently trying to setup a Custom Fact that will can be used to determine the version of the Java JRE running on a machine, in order to use it in my manifests to ensure the proper JARS are distribured based on environment. I''m trying to use the java -version command and then capture the JRE release (eg "1.6.0_37"). No matter what I have tried, the output

This commit starts to split our massive, monolithic configure.ac file into smaller files, using the m4_include mechanism to combine them. I don't know if we should really do this, so I'm open to comments about it. However: - Our configure.ac script is 1800+ lines long, and that's pretty long. - configure.ac lacks structure; splitting it up might improve that. - From what I read,

Two (not related to each other) refactorings: Patches 1-12 split configure.ac into smaller files using the m4_include mechanism. Patches 13-15 split out parts of guestfs.pod (ie. guestfs(3)) into three new manual pages: guestfs-hacking(3) - how to extend and contribute to libguestfs guestfs-internals(3) - architecture and internals guestfs-security(3) - security and CVEs Patch 16 is a