How to use JavaCompiler from tools.jar without JDK
up vote
1
down vote
favorite
I am trying to create an application that can compile a provided .java
file during runtime. I understand that there is a programmatical compiler available within the tools.jar
of the JDK. However, I cannot guarantee that the user of the application has JDK. I have attempted to package tools.jar
within the application and reference it as a library. This seems to work within the Eclipse IDE when I have tools.jar
added into the Bootstrap Entries of the classpath. When exporting the application to a runnable jar (with tools.jar
packaged with it),
ToolProvider.getSystemJavaCompiler();
returns null
. I am not exactly sure what the issue is, but I believe it may have to do with the Bootstrap Entries of the classpath not being properly preserved when the application is exported to a runnable jar. Any ideas? Are there any alternatives to the tools.jar
compiler that I could use? Thanks for your patience, as this is my first question posted here!
java eclipse classpath javacompiler tools.jar
add a comment |
up vote
1
down vote
favorite
I am trying to create an application that can compile a provided .java
file during runtime. I understand that there is a programmatical compiler available within the tools.jar
of the JDK. However, I cannot guarantee that the user of the application has JDK. I have attempted to package tools.jar
within the application and reference it as a library. This seems to work within the Eclipse IDE when I have tools.jar
added into the Bootstrap Entries of the classpath. When exporting the application to a runnable jar (with tools.jar
packaged with it),
ToolProvider.getSystemJavaCompiler();
returns null
. I am not exactly sure what the issue is, but I believe it may have to do with the Bootstrap Entries of the classpath not being properly preserved when the application is exported to a runnable jar. Any ideas? Are there any alternatives to the tools.jar
compiler that I could use? Thanks for your patience, as this is my first question posted here!
java eclipse classpath javacompiler tools.jar
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to create an application that can compile a provided .java
file during runtime. I understand that there is a programmatical compiler available within the tools.jar
of the JDK. However, I cannot guarantee that the user of the application has JDK. I have attempted to package tools.jar
within the application and reference it as a library. This seems to work within the Eclipse IDE when I have tools.jar
added into the Bootstrap Entries of the classpath. When exporting the application to a runnable jar (with tools.jar
packaged with it),
ToolProvider.getSystemJavaCompiler();
returns null
. I am not exactly sure what the issue is, but I believe it may have to do with the Bootstrap Entries of the classpath not being properly preserved when the application is exported to a runnable jar. Any ideas? Are there any alternatives to the tools.jar
compiler that I could use? Thanks for your patience, as this is my first question posted here!
java eclipse classpath javacompiler tools.jar
I am trying to create an application that can compile a provided .java
file during runtime. I understand that there is a programmatical compiler available within the tools.jar
of the JDK. However, I cannot guarantee that the user of the application has JDK. I have attempted to package tools.jar
within the application and reference it as a library. This seems to work within the Eclipse IDE when I have tools.jar
added into the Bootstrap Entries of the classpath. When exporting the application to a runnable jar (with tools.jar
packaged with it),
ToolProvider.getSystemJavaCompiler();
returns null
. I am not exactly sure what the issue is, but I believe it may have to do with the Bootstrap Entries of the classpath not being properly preserved when the application is exported to a runnable jar. Any ideas? Are there any alternatives to the tools.jar
compiler that I could use? Thanks for your patience, as this is my first question posted here!
java eclipse classpath javacompiler tools.jar
java eclipse classpath javacompiler tools.jar
asked Nov 14 at 2:22
rgoulazian
82
82
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
You need to use the compiler within "tools.jar"
ToolProvider.getSystemJavaCompiler()
will return the compiler from the jdk defined in the path variable,
you can do this instead:
File file = new File(pathToToolsJar);
URL urls = new URL{ file.toURI().toURL() };
ClassLoader loader = new URLClassLoader(urls);
Class compilerClass = loader.loadClass("com.sun.tools.javac.api.JavacTool");
JavaCompiler compiler = (JavaCompiler) compilerClass.getConstructor().newInstance();
Or you can add tools.jar as a library at compile time
import com.sun.tools.javac.api.JavacTool;
...
JavaCompiler compiler = new JavacTool();
Or you can change System properties, but that leads to unexpected behaviors
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old wayimport com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
You need to use the compiler within "tools.jar"
ToolProvider.getSystemJavaCompiler()
will return the compiler from the jdk defined in the path variable,
you can do this instead:
File file = new File(pathToToolsJar);
URL urls = new URL{ file.toURI().toURL() };
ClassLoader loader = new URLClassLoader(urls);
Class compilerClass = loader.loadClass("com.sun.tools.javac.api.JavacTool");
JavaCompiler compiler = (JavaCompiler) compilerClass.getConstructor().newInstance();
Or you can add tools.jar as a library at compile time
import com.sun.tools.javac.api.JavacTool;
...
JavaCompiler compiler = new JavacTool();
Or you can change System properties, but that leads to unexpected behaviors
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old wayimport com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
add a comment |
up vote
1
down vote
accepted
You need to use the compiler within "tools.jar"
ToolProvider.getSystemJavaCompiler()
will return the compiler from the jdk defined in the path variable,
you can do this instead:
File file = new File(pathToToolsJar);
URL urls = new URL{ file.toURI().toURL() };
ClassLoader loader = new URLClassLoader(urls);
Class compilerClass = loader.loadClass("com.sun.tools.javac.api.JavacTool");
JavaCompiler compiler = (JavaCompiler) compilerClass.getConstructor().newInstance();
Or you can add tools.jar as a library at compile time
import com.sun.tools.javac.api.JavacTool;
...
JavaCompiler compiler = new JavacTool();
Or you can change System properties, but that leads to unexpected behaviors
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old wayimport com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
You need to use the compiler within "tools.jar"
ToolProvider.getSystemJavaCompiler()
will return the compiler from the jdk defined in the path variable,
you can do this instead:
File file = new File(pathToToolsJar);
URL urls = new URL{ file.toURI().toURL() };
ClassLoader loader = new URLClassLoader(urls);
Class compilerClass = loader.loadClass("com.sun.tools.javac.api.JavacTool");
JavaCompiler compiler = (JavaCompiler) compilerClass.getConstructor().newInstance();
Or you can add tools.jar as a library at compile time
import com.sun.tools.javac.api.JavacTool;
...
JavaCompiler compiler = new JavacTool();
Or you can change System properties, but that leads to unexpected behaviors
You need to use the compiler within "tools.jar"
ToolProvider.getSystemJavaCompiler()
will return the compiler from the jdk defined in the path variable,
you can do this instead:
File file = new File(pathToToolsJar);
URL urls = new URL{ file.toURI().toURL() };
ClassLoader loader = new URLClassLoader(urls);
Class compilerClass = loader.loadClass("com.sun.tools.javac.api.JavacTool");
JavaCompiler compiler = (JavaCompiler) compilerClass.getConstructor().newInstance();
Or you can add tools.jar as a library at compile time
import com.sun.tools.javac.api.JavacTool;
...
JavaCompiler compiler = new JavacTool();
Or you can change System properties, but that leads to unexpected behaviors
edited Nov 14 at 3:10
answered Nov 14 at 2:41
Juan
525
525
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old wayimport com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
add a comment |
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old wayimport com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Thanks for the fast response. This seems to work perfectly. Any chance I could get a brief explanation as to what the alternative is doing?
– rgoulazian
Nov 14 at 3:00
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old way
import com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
Uhm, I'm not really sure why I suggested to use reflection, you could just add tools.jar as a library and instance it the old way
import com.sun.tools.javac.api.JavacTool;
JavaCompiler compiler = new JavacTool();
– Juan
Nov 14 at 3:06
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
What I suggested originaly was to load tools.jar at runtime using reflection; Using URLClassLoader is an easy way to load dependencies at runtime, you just ask the loader for the class you want, and it looks in the urls you specified for the class
– Juan
Nov 14 at 3:11
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53292291%2fhow-to-use-javacompiler-from-tools-jar-without-jdk%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown