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!










share|improve this question


























    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!










    share|improve this question
























      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!










      share|improve this question













      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






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 14 at 2:22









      rgoulazian

      82




      82
























          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






          share|improve this answer























          • 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












          • 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













          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          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

























          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






          share|improve this answer























          • 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












          • 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

















          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






          share|improve this answer























          • 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












          • 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















          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






          share|improve this answer














          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







          share|improve this answer














          share|improve this answer



          share|improve this answer








          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 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




















          • 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












          • 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




















          draft saved

          draft discarded




















































          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.




          draft saved


          draft discarded














          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





















































          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







          Popular posts from this blog

          How to change which sound is reproduced for terminal bell?

          Can I use Tabulator js library in my java Spring + Thymeleaf project?

          Title Spacing in Bjornstrup Chapter, Removing Chapter Number From Contents