Bug #10361 | The second paragraph on page -- | ||
---|---|---|---|
Submitted: | 4 May 2005 16:06 | Modified: | 18 Jul 2005 22:48 |
Reporter: | Shay Atzitz | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / MXJ Documentation | Severity: | S3 (Non-critical) |
Version: | OS: | ||
Assigned to: | Mike Hillyer | CPU Architecture: | Any |
[4 May 2005 16:06]
Shay Atzitz
[4 May 2005 16:12]
Mark Matthews
> In a previous Version of the J/Connector (3.0.15), there was an > instruction > that a user can either add the ".jar" file to the classpath, or copy > the > ".jar" file to the "$JAVA_HOME/jre/lib/ext" directory. > > The option to copy the file to the "$JAVA_HOME/jre/lib/ext" > directory, is no longer specified in the J/Connector document > (3.1.8a) on page: > http://dev.mysql.com/doc/connector/j/en/cj-classpath.html > > Is there a reason for that ? Yes. > If so - What is the reason ? It causes more problems than it solves, and is actively being discouraged by Sun and other third-party vendors. It often leads to hard-to-solve classpath errors where new versions of the driver that get installed in more "standard" places don't get used. -Mark
[4 May 2005 16:15]
Mark Matthews
> And a third one is: > The tar.gz file contains 2 ".jar" files, one of them with a "-g" > extension > to the filename (connector[version]bin-g.jar). > What is the difference between the files - and which of them should I > Use ? -g.jar is for debugging and includes trace functionality. > There's nothing about that in the DOCs Being fixed for 3.1.9. As an aside, please don't open one bug for three separate issues, this should really be three bugs.
[12 Jul 2005 5:11]
Jorge del Conde
docs fixed