2013-06-03 14:44:10 +00:00
#!/bin/sh
2007-12-01 00:00:00 +00:00
# @test MultipleJRE.sh
2014-12-17 00:02:56 +00:00
# @bug 4811102 4953711 4955505 4956301 4991229 4998210 5018605 6387069 6733959 8058407 8067421
2007-12-01 00:00:00 +00:00
# @build PrintVersion
# @build UglyPrintVersion
2008-09-04 16:43:32 +00:00
# @build ZipMeUp
2007-12-01 00:00:00 +00:00
# @run shell MultipleJRE.sh
2014-11-10 16:43:27 +00:00
# @summary Verify Multiple JRE version support has been removed
2007-12-01 00:00:00 +00:00
# @author Joseph E. Kowalski
#
2014-12-17 00:02:56 +00:00
# Copyright (c) 2003, 2014, Oracle and/or its affiliates. All rights reserved.
2007-12-01 00:00:00 +00:00
# DO NOT ALTER OR REMOVE COPYRIGHT NOTICES OR THIS FILE HEADER.
#
# This code is free software; you can redistribute it and/or modify it
# under the terms of the GNU General Public License version 2 only, as
# published by the Free Software Foundation.
#
# This code is distributed in the hope that it will be useful, but WITHOUT
# ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or
# FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License
# version 2 for more details (a copy is included in the LICENSE file that
# accompanied this code).
#
# You should have received a copy of the GNU General Public License version
# 2 along with this work; if not, write to the Free Software Foundation,
# Inc., 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA.
#
2010-05-25 22:58:33 +00:00
# Please contact Oracle, 500 Oracle Parkway, Redwood Shores, CA 94065 USA
# or visit www.oracle.com if you need additional information or have any
# questions.
2007-12-01 00:00:00 +00:00
#
# Verify directory context variables are set
if [ " ${ TESTJAVA } " = "" ]
then
echo "TESTJAVA not set. Test cannot execute. Failed."
exit 1
fi
2013-01-11 20:19:55 +00:00
if [ " ${ COMPILEJAVA } " = "" ] ; then
COMPILEJAVA = " ${ TESTJAVA } "
fi
2007-12-01 00:00:00 +00:00
if [ " ${ TESTSRC } " = "" ]
then
echo "TESTSRC not set. Test cannot execute. Failed."
exit 1
fi
if [ " ${ TESTCLASSES } " = "" ]
then
echo "TESTCLASSES not set. Test cannot execute. Failed."
exit 1
fi
2012-12-13 14:47:35 +00:00
JAVAEXE = " $TESTJAVA /bin/java ${ TESTVMOPTS } "
JAVA = " $TESTJAVA /bin/java ${ TESTVMOPTS } -classpath $TESTCLASSES "
2013-01-11 20:19:55 +00:00
JAR = " $COMPILEJAVA /bin/jar ${ TESTTOOLVMOPTS } "
2007-12-01 00:00:00 +00:00
OS = ` uname -s` ;
2008-09-04 16:43:32 +00:00
#
# Tests whether we are on windows (true) or not.
#
IsWindows( ) {
case " $OS " in
Windows* | CYGWIN* )
printf "true"
; ;
* )
printf "false"
; ;
esac
}
2007-12-01 00:00:00 +00:00
#
# Shell routine to test for the proper rejection of syntactically incorrect
# version specifications.
#
TestSyntax( ) {
mess = " ` $JAVA -version:\" $1 \" -version 2>&1` "
if [ $? -eq 0 ] ; then
echo " Invalid version syntax $1 accepted "
exit 1
fi
prefix = "`echo " $mess " | cut -d ' ' -f 1-3`"
if [ " $prefix " != "Error: Syntax error" ] ; then
echo " Unexpected error message for invalid syntax $1 "
exit 1
fi
}
#
# Just as the name says. We sprinkle these in the appropriate location
# in the test file system and they just say who they are pretending to be.
#
CreateMockVM( ) {
mkdir -p jdk/j2re$1 /bin
echo "#!/bin/sh" > jdk/j2re$1 /bin/java
echo " echo \" $1 \" " >> jdk/j2re$1 /bin/java
chmod +x jdk/j2re$1 /bin/java
}
#
# Constructs the jar file needed by these tests.
#
CreateJar( ) {
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo "Main-Class: PrintVersion" >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
fi
cp $TESTCLASSES /PrintVersion.class .
$JAR $2 cmf META-INF/MANIFEST.MF PrintVersion PrintVersion.class
}
#
# Constructs a jar file using zip.
#
CreateZippyJar( ) {
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo "Main-Class: PrintVersion" >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
fi
cp $TESTCLASSES /PrintVersion.class .
/usr/bin/zip $2 PrintVersion META-INF/MANIFEST.MF PrintVersion.class
}
#
# Constructs a jar file with a Main-Class attribute of greater than
# 80 characters to validate the continuation line processing.
#
# Make this just long enough to require two continuation lines. Longer
# paths take too much away from the restricted Windows maximum path length.
# Note: see the variable UGLYCLASS and its check for path length.
#
# Make sure that 5018605 remains fixed by including additional sections
# in the Manifest which contain the same names as those allowed in the
# main section.
#
PACKAGE = reallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallyreallylongpackagename
UGLYCLASS = $TESTCLASSES /$PACKAGE /UglyPrintVersion.class
CreateUglyJar( ) {
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo " Main-Class: $PACKAGE .UglyPrintVersion " >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
fi
echo "" >> META-INF/MANIFEST.MF
echo "Name: NotToBeFound.class" >> META-INF/MANIFEST.MF
echo "Main-Class: NotToBeFound" >> META-INF/MANIFEST.MF
mkdir -p $PACKAGE
cp $UGLYCLASS $PACKAGE
$JAR $2 cmf META-INF/MANIFEST.MF PrintVersion \
$PACKAGE /UglyPrintVersion.class
}
#
# Constructs a jar file with a fair number of "zip directory" entries and
# the MANIFEST.MF entry at or near the end of that directory to validate
# the ability to transverse that directory.
#
CreateFullJar( ) {
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo "Main-Class: PrintVersion" >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
fi
cp $TESTCLASSES /PrintVersion.class .
for i in 0 1 2 3 4 5 6 7 8 9 ; do
for j in 0 1 2 3 4 5 6 7 8 9 ; do
touch AfairlyLongNameEatsUpDirectorySpaceBetter$i $j
done
done
$JAR $2 cMf PrintVersion PrintVersion.class AfairlyLong*
$JAR $2 umf META-INF/MANIFEST.MF PrintVersion
rm -f AfairlyLong*
}
#
# Creates a jar file with the attributes which caused the failure
# described in 4991229.
#
# Generate a bunch of CENTAB entries, each of which is 64 bytes long
# which practically guarentees we will hit the appropriate power of
# two buffer (initially 1K). Note that due to the perversity of
# zip/jar files, the first entry gets extra stuff so it needs a
# shorter name to compensate.
#
CreateAlignedJar( ) {
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo "Main-Class: PrintVersion" >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
fi
cp $TESTCLASSES /PrintVersion.class .
touch 57BytesSpecial
for i in 0 1 2 3 4 5 6 7 8 9 ; do
for j in 0 1 2 3 4 5 6 7 8 9 ; do
touch 64BytesPerEntry-$i $j
done
done
$JAR $2 cMf PrintVersion 57* 64* PrintVersion.class
$JAR $2 umf META-INF/MANIFEST.MF PrintVersion
rm -f 57* 64*
}
#
# Adds comments to a jar/zip file. This serves two purposes:
#
# 1) Make sure zip file comments (both per file and per archive) are
# properly processed and ignored.
#
# 2) A long file comment creates a mondo "Central Directory" entry in
# the zip file. Such a "mondo" entry could also be due to a very
# long file name (path) or a long "Ext" entry, but adding the long
# comment is the easiest way.
#
2014-11-10 16:43:27 +00:00
MONDO = " Mondo comment line 00 is designed to take up space - lots and lots of space. Mondo comment line 01 is designed to take up space - lots and lots of space. Mondo comment line 02 is designed to take up space - lots and lots of space. Mondo comment line 03 is designed to take up space - lots and lots of space. Mondo comment line 04 is designed to take up space - lots and lots of space. Mondo comment line 05 is designed to take up space - lots and lots of space. Mondo comment line 06 is designed to take up space - lots and lots of space. Mondo comment line 07 is designed to take up space - lots and lots of space. Mondo comment line 08 is designed to take up space - lots and lots of space. Mondo comment line 09 is designed to take up space - lots and lots of space. Mondo comment line 0a is designed to take up space - lots and lots of space. Mondo comment line 0b is designed to take up space - lots and lots of space. Mondo comment line 0c is designed to take up space - lots and lots of space. Mondo comment line 0d is designed to take up space - lots and lots of space. Mondo comment line 0e is designed to take up space - lots and lots of space. Mondo comment line 0f is designed to take up space - lots and lots of space. Mondo comment line 10 is designed to take up space - lots and lots of space. Mondo comment line 11 is designed to take up space - lots and lots of space. Mondo comment line 12 is designed to take up space - lots and lots of space. Mondo comment line 13 is designed to take up space - lots and lots of space. Mondo comment line 14 is designed to take up space - lots and lots of space. Mondo comment line 15 is designed to take up space - lots and lots of space. Mondo comment line 16 is designed to take up space - lots and lots of space. Mondo comment line 17 is designed to take up space - lots and lots of space. Mondo comment line 18 is designed to take up space - lots and lots of space. Mondo comment line 19 is designed to take up space - lots and lots of space. Mondo comment line 1a is designed to take up space - lots and lots of space. Mondo comment line 1b is designed to take up space - lots and lots of space. Mondo comment line 1c is designed to take up space - lots and lots of space. Mondo comment line 1d is designed to take up space - lots and lots of space. Mondo comment line 1e is designed to take up space - lots and lots of space. Mondo comment line 1f is designed to take up space - lots and lots of space. Mondo comment line 20 is designed to take up space - lots and lots of space. Mondo comment line 21 is designed to take up space - lots and lots of space. Mondo comment line 22 is designed to take up space - lots and lots of space. Mondo comment line 23 is designed to take up space - lots and lots of space. Mondo comment line 24 is designed to take up space - lots and lots of space. Mondo comment line 25 is designed to take up space - lots and lots of space. Mondo comment line 26 is designed to take up space - lots and lots of space. Mondo comment line 27 is designed to take up space - lots and lots of space. Mondo comment line 28 is designed to take up space - lots and lots of space. Mondo comment line 29 is designed to take up space - lots and lots of space. Mondo comment line 2a is designed to take up space - lots and lots of space. Mondo comment line 2b is designed to take up space - lots and lots of space. Mondo comment line 2c is designed to take up space - lots and lots of space. Mondo comment line 2d is designed to take up space - lots and lots of space. Mondo comment line 2e is designed to take up space - lots and lots of space. Mondo comment line 2f is designed to take up space - lots and lots of space. Mondo comment line 30 is designed to take up space - lots and lots of space. Mondo comment line 31 is designed to take up space - lots and lots of space. Mondo comment line 32 is designed to take up space - lots and lots of space. Mondo comment line 33 is designed to take up space - lots and lots of space. Mondo comment line 34 is design
2007-12-01 00:00:00 +00:00
CommentZipFile( ) {
2014-11-10 16:43:27 +00:00
mkdir -p META-INF
echo "Manifest-Version: 1.0" > META-INF/MANIFEST.MF
echo "Main-Class: PrintVersion" >> META-INF/MANIFEST.MF
if [ " $1 " != "" ] ; then
echo " JRE-Version: $1 " >> META-INF/MANIFEST.MF
2007-12-01 00:00:00 +00:00
fi
2014-11-10 16:43:27 +00:00
cp $TESTCLASSES /PrintVersion.class .
# The remaining code in CommentZipFile essentially replaces the
# following code, which added comments to the jar file.
# Unfortunately zipnote has been broken since 3.0 [ 2008 ] and
# there has been no new [ fixed ] version. zipnote has probably
# always failed, or failed for a long time without causing the
# test to fail. So no comments were added to the file.
# The comments are added using zip(1) during the creation of the
# zip file.
#
# NOTE:
# It seems the original intent of this test was to add a very long
# comment for one file. But zip allows a max of 256 characters, so
# we settle for adding 256-character comments to lots of files.
#
# $JAR $2cMf PrintVersion PrintVersion.class AfairlyLong*
# $JAR $2umf META-INF/MANIFEST.MF PrintVersion
# /usr/bin/zipnote PrintVersion.zip > zipout
# ... code to modify zipout adding comments
# /usr/bin/zipnote -w PrintVersion.zip < zipin
# mv PrintVersion.zip PrintVersion
#
for i in 0 1 2 3 4 5 6 7 8 9 ; do
for j in 0 1 2 3 4 5 6 7 8 9 ; do
touch AfairlyLongNameEatsUpDirectorySpaceBetter$i $j
done
done
zip -$2 c PrintVersion.zip PrintVersion.class AfairlyLong* META-INF/MANIFEST.MF << FINI
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
File Comment Line.
$MONDO
File Comment Line.
File Comment Line.
File Comment Line.
FINI
rm -f AfairlyLong*
2007-12-01 00:00:00 +00:00
mv PrintVersion.zip PrintVersion
2014-11-10 16:43:27 +00:00
2007-12-01 00:00:00 +00:00
}
#
# Attempt to launch a vm using a version specifier and make sure the
# resultant launch (probably a "mock vm") is appropriate.
#
LaunchVM( ) {
if [ " $1 " != "" ] ; then
2014-11-10 16:43:27 +00:00
mess = " ` $JAVA \" $1 \" -jar PrintVersion 2>&1` "
if [ $? -eq 0 ] ; then
echo " Unexpected success of -Version: $1 "
echo " $mess "
exit 1
fi
2007-12-01 00:00:00 +00:00
else
mess = " ` $JAVA -jar PrintVersion 2>&1` "
2014-11-10 16:43:27 +00:00
if [ $? -ne 0 ] ; then
prefix = ` echo " $mess " | cut -d ' ' -f 1-3`
if [ " $prefix " != "Unable to locate" ] ; then
echo " $mess "
exit 1
fi
echo " Unexpected error in attempting to locate $1 "
2007-12-01 00:00:00 +00:00
exit 1
fi
2014-11-10 16:43:27 +00:00
2007-12-01 00:00:00 +00:00
fi
2014-11-10 16:43:27 +00:00
2007-12-01 00:00:00 +00:00
echo $mess | grep " $2 " > /dev/null 2>& 1
if [ $? != 0 ] ; then
2014-11-10 16:43:27 +00:00
echo " Launched $mess , expected $1 "
2007-12-01 00:00:00 +00:00
exit 1
fi
}
2008-09-04 16:43:32 +00:00
# Tests very long Main-Class attribute in the jar
TestLongMainClass( ) {
JVER = $1
if [ " $JVER " = "mklink" ] ; then
JVER = XX
JDKXX = jdk/j2re$JVER
rm -rf jdk
mkdir jdk
ln -s $TESTJAVA $JDKXX
JAVA_VERSION_PATH = "`pwd`/jdk"
export JAVA_VERSION_PATH
fi
$JAVAEXE -cp $TESTCLASSES ZipMeUp UglyBetty.jar 4097
message = " ` $JAVAEXE -version: $JVER -jar UglyBetty.jar 2>&1` "
echo $message | grep "Error: main-class: attribute exceeds system limits" > /dev/null 2>& 1
if [ $? -ne 0 ] ; then
printf "Long manifest test did not get expected error"
exit 1
fi
unset JAVA_VERSION_PATH
rm -rf jdk
}
2007-12-01 00:00:00 +00:00
#
# Main test sequence starts here
#
2014-11-10 16:43:27 +00:00
2007-12-01 00:00:00 +00:00
RELEASE = ` $JAVA -version 2>& 1 | head -n 1 | cut -d ' ' -f 3 | \
sed -e "s/\"//g" `
BASE_RELEASE = ` echo $RELEASE | sed -e "s/-.*//g" `
#
# Make sure that the generic jar/manifest reading code works. Test both
# compressed and "stored" jar files.
#
# The "Ugly" jar (long manifest line) tests are only run if the combination
# of the file name length restrictions and the length of the cwd allow it.
#
CreateJar "" ""
LaunchVM "" " ${ RELEASE } "
CreateJar "" "0"
LaunchVM "" " ${ RELEASE } "
2008-09-04 16:43:32 +00:00
if [ ` IsWindows` = "true" ] ; then
MAXIMUM_PATH = 255;
else
MAXIMUM_PATH = 1024;
fi
2007-12-01 00:00:00 +00:00
PATH_LENGTH = ` printf "%s" " $UGLYCLASS " | wc -c`
if [ ${ PATH_LENGTH } -lt ${ MAXIMUM_PATH } ] ; then
CreateUglyJar "" ""
LaunchVM "" " ${ RELEASE } "
CreateUglyJar "" "0"
LaunchVM "" " ${ RELEASE } "
else
printf "Warning: Skipped UglyJar test, path length exceeded, %d" $MAXIMUM_PATH
printf " allowed, the current path is %d\n" $PATH_LENGTH
fi
CreateAlignedJar "" ""
LaunchVM "" " ${ RELEASE } "
CreateFullJar "" ""
LaunchVM "" " ${ RELEASE } "
#
# 4998210 shows that some very strange behaviors are semi-supported.
# In this case, it's the ability to prepend any kind of stuff to the
# jar file and require that the jar file still work. Note that this
# "interface" isn't publically supported and we may choose to break
# it in the future, but this test guarantees that we won't break it
# without informed consent. We take advantage the fact that the
# "FullJar" we just tested is probably the best jar to begin with
# for this test.
#
echo "This is just meaningless bytes to prepend to the jar" > meaningless
mv PrintVersion meaningfull
cat meaningless meaningfull > PrintVersion
LaunchVM "" " ${ RELEASE } "
rm meaningless meaningfull
#
# Officially, one must use "the jar command to create a jar file. However,
# all the comments about jar commands **imply** that jar files and zip files
# are equivalent. (Note: this isn't true due to the "0xcafe" insertion.)
# On systems which have a command line zip, test the ability to use zip
# to construct a jar and then use it (6387069).
#
if [ -x /usr/bin/zip ] ; then
CreateZippyJar "" "-q"
LaunchVM "" " ${ RELEASE } "
fi
#
# jar files shouldn't have comments, but it is possible that somebody added
# one by using zip -c, zip -z, zipnote or a similar utility. On systems
# that have "zipnote", verify this functionality.
#
# This serves a dual purpose of creating a very large "central directory
# entry" which validates to code to read such entries.
#
if [ -x /usr/bin/zipnote ] ; then
CreateFullJar "" ""
CommentZipFile "AfairlyLongNameEatsUpDirectorySpaceBetter20"
LaunchVM "" " ${ RELEASE } "
fi
2014-12-17 00:02:56 +00:00
exit 0
