Where is tools jar located

On windows, I could find it at jdk1. You can find java directory structure here. The default Java class loader cannot find an embedded jar inside a jar file. You will need to set your Java program to use a class loader which can deal with embedded jar files. As fas as I know, I have not seen one in any opensource libraries so you may need to write one yourself. Active 4 years, 7 months ago. Viewed 19k times. Improve this question.

Community Bot 1. You don't want to put a! This has the side effect of starting another shell, doing your export commands and then exiting once done which won't source anything into your shell. Look at the other files in that directory as references. G-Man Thank you for your suggestion. Why should we not do anything as root?

Add a comment. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. The Overflow Blog. Podcast Explaining the semiconductor shortage, and how it might end. Does ES6 make JavaScript frameworks obsolete? Featured on Meta. Now live: A fully responsive profile. Linked Related 2. Hot Network Questions. Question feed. This type of JAR file is searched at the point that it appears, which is earlier in the class path. All of the classes required by an extension are presumed to be part of the JDK or to have been installed as extension.

The javac and javadoc commands use class files in the following two ways:. To run, the javac and javadoc commands must load various class files. To process the source code they operate on, the javac and javadoc commands must obtain information on object types used in the source code.

The class files used to resolve source code references are mostly the same class files used to run the javac and javadoc commands.

But there are some important exceptions, as follows:. Both the javac and javadoc commands often resolve references to classes and interfaces that have nothing to do with the implementation of the javac or javadoc commands. Information on referenced user classes and interfaces might be present in the form of class files, source code files, or both.

The tools classes in the tools. The tools classes are not used to resolve source code references unless the tools. A programmer might want to resolve boot class or extension class references with an alternative Java platform implementation. Both the javac and javadoc commands support this with their -bootclasspath and -extdirs options. Use of these options does not modify the set of class files used to run the javac or javadoc commands themselves.

If a referenced class is defined in both a class file and a source file, the javadoc command always uses the source file. The javadoc command never compiles source files. In the same situation the javac command uses class files, but automatically recompiles any class files it determines to be out of date. The rules for automatic recompilation are documented in javac. By default, the javac and javadoc commands search the user class path for both class files and source code files.

If the -sourcepath option is specified, the javac and javadoc commands search for source files only on the specified source file path, while still searching the user class path for class files.