[svn] 4295: Move @see tag in ASDoc comment to work around SDK-18256

Question

Revision: 4295
Author: [email protected]
Date: 2008-12-12 08:57:11 -0800 (Fri, 12 Dec 2008)
Log Message:
Move @see tag in ASDoc comment to work around SDK-18256
QE Notes: None
Doc Notes: None
Bugs: -
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-18256
Modified Paths:
flex/sdk/trunk/frameworks/projects/framework/src/mx/printing/PrintDataGrid.as

Answer 1

Submitted On 04-MAY-2007
exaid6
Further investigation reveals that if I unpack the jar file in a directory (jar xvf xxxx.jar) and change the classpath to "." instead of the jarfile, the program launches perfectly. This is definintely a bug in the classpath handling of big jar files on certain systems, or something of that sort. (Note: I'm using java sdk 6u1, 32 bit CentOS Linux.)
Submitted On 27-SEP-2007
I've encountered the same problem on RH FC6.
If you take a look at the script you will see this line tail +368 "$0" which attempts to extract the remaining lines into a separate jar file. This line may not work on all versions of Linux. A proper way to use Linux version of tail utility is: tail -n +368 "$0". Anyways, you can manually extract the jar file if you are getting tail +368 file not found error message when running the script.
After you extract the jar file you can run it via the command line like so
java -classpath .:./tmp/jwsdp.jar -Djava.ext.dirs= -D.java.endorsed.dirs= -Dtemp.dir=/opt/java/jwsdp/tmp -Dis.debug=1 JWSDP
You should be able to install JWSDP 2.0 successfully on your Linux machine.