Maven/Gradle set environment variable for compilation?










0















I developed an annotation processor that would optionally require the artifactId of the project to generate a file. I am using an environment variable (GRAPHDEP_USAGE) to get the value.



I can set the environment variable from shell before launching Maven/Gradle, but I would like the build tool to set the environment variable for me before the compilation instead:



  • For Maven, inside the pom.xml i would like to populate the environment variable GRAPHDEP_PROJECT with the content of $artifactId, before launching the compile goal.

  • For Gradle, inside the build.gradle i would like to populate the environment variable GRAPHDEP_PROJECT with the content of project.name, before launching the task compileJava.

I tried a few options without success. Any idea how i can do that?










share|improve this question






















  • If you write a Maven plugin, you get the artifactId for free.

    – JF Meier
    Nov 12 '18 at 15:40















0















I developed an annotation processor that would optionally require the artifactId of the project to generate a file. I am using an environment variable (GRAPHDEP_USAGE) to get the value.



I can set the environment variable from shell before launching Maven/Gradle, but I would like the build tool to set the environment variable for me before the compilation instead:



  • For Maven, inside the pom.xml i would like to populate the environment variable GRAPHDEP_PROJECT with the content of $artifactId, before launching the compile goal.

  • For Gradle, inside the build.gradle i would like to populate the environment variable GRAPHDEP_PROJECT with the content of project.name, before launching the task compileJava.

I tried a few options without success. Any idea how i can do that?










share|improve this question






















  • If you write a Maven plugin, you get the artifactId for free.

    – JF Meier
    Nov 12 '18 at 15:40













0












0








0








I developed an annotation processor that would optionally require the artifactId of the project to generate a file. I am using an environment variable (GRAPHDEP_USAGE) to get the value.



I can set the environment variable from shell before launching Maven/Gradle, but I would like the build tool to set the environment variable for me before the compilation instead:



  • For Maven, inside the pom.xml i would like to populate the environment variable GRAPHDEP_PROJECT with the content of $artifactId, before launching the compile goal.

  • For Gradle, inside the build.gradle i would like to populate the environment variable GRAPHDEP_PROJECT with the content of project.name, before launching the task compileJava.

I tried a few options without success. Any idea how i can do that?










share|improve this question














I developed an annotation processor that would optionally require the artifactId of the project to generate a file. I am using an environment variable (GRAPHDEP_USAGE) to get the value.



I can set the environment variable from shell before launching Maven/Gradle, but I would like the build tool to set the environment variable for me before the compilation instead:



  • For Maven, inside the pom.xml i would like to populate the environment variable GRAPHDEP_PROJECT with the content of $artifactId, before launching the compile goal.

  • For Gradle, inside the build.gradle i would like to populate the environment variable GRAPHDEP_PROJECT with the content of project.name, before launching the task compileJava.

I tried a few options without success. Any idea how i can do that?







java maven gradle annotation-processing






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Nov 12 '18 at 9:56









GauthierGauthier

2,3071822




2,3071822












  • If you write a Maven plugin, you get the artifactId for free.

    – JF Meier
    Nov 12 '18 at 15:40

















  • If you write a Maven plugin, you get the artifactId for free.

    – JF Meier
    Nov 12 '18 at 15:40
















If you write a Maven plugin, you get the artifactId for free.

– JF Meier
Nov 12 '18 at 15:40





If you write a Maven plugin, you get the artifactId for free.

– JF Meier
Nov 12 '18 at 15:40












1 Answer
1






active

oldest

votes


















0














Not exactly answering the question, but actually answering the question behind which was how to pass arguments to annotation processors.




Compiler arguments can be specified with -A flag.



In Gradle:



compileJava.options.compilerArgs += "-Agraphdep.project=$project.name"


In Maven:



<compilerArgs>
<arg>-Agraphdep.project=$project.artifactId</arg>
</compilerArgs>


Then from within an implementation of AbstractProcessor it is possible to retrieve the arguments using:



processingEnv.getOptions().get("widget");


The options supported must be declared by the processor, either by using the annotation @SupportedOptions("widget") or by overriding the method public Set<String> getSupportedOptions().






share|improve this answer






















    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',
    autoActivateHeartbeat: false,
    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%2f53259684%2fmaven-gradle-set-environment-variable-for-compilation%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









    0














    Not exactly answering the question, but actually answering the question behind which was how to pass arguments to annotation processors.




    Compiler arguments can be specified with -A flag.



    In Gradle:



    compileJava.options.compilerArgs += "-Agraphdep.project=$project.name"


    In Maven:



    <compilerArgs>
    <arg>-Agraphdep.project=$project.artifactId</arg>
    </compilerArgs>


    Then from within an implementation of AbstractProcessor it is possible to retrieve the arguments using:



    processingEnv.getOptions().get("widget");


    The options supported must be declared by the processor, either by using the annotation @SupportedOptions("widget") or by overriding the method public Set<String> getSupportedOptions().






    share|improve this answer



























      0














      Not exactly answering the question, but actually answering the question behind which was how to pass arguments to annotation processors.




      Compiler arguments can be specified with -A flag.



      In Gradle:



      compileJava.options.compilerArgs += "-Agraphdep.project=$project.name"


      In Maven:



      <compilerArgs>
      <arg>-Agraphdep.project=$project.artifactId</arg>
      </compilerArgs>


      Then from within an implementation of AbstractProcessor it is possible to retrieve the arguments using:



      processingEnv.getOptions().get("widget");


      The options supported must be declared by the processor, either by using the annotation @SupportedOptions("widget") or by overriding the method public Set<String> getSupportedOptions().






      share|improve this answer

























        0












        0








        0







        Not exactly answering the question, but actually answering the question behind which was how to pass arguments to annotation processors.




        Compiler arguments can be specified with -A flag.



        In Gradle:



        compileJava.options.compilerArgs += "-Agraphdep.project=$project.name"


        In Maven:



        <compilerArgs>
        <arg>-Agraphdep.project=$project.artifactId</arg>
        </compilerArgs>


        Then from within an implementation of AbstractProcessor it is possible to retrieve the arguments using:



        processingEnv.getOptions().get("widget");


        The options supported must be declared by the processor, either by using the annotation @SupportedOptions("widget") or by overriding the method public Set<String> getSupportedOptions().






        share|improve this answer













        Not exactly answering the question, but actually answering the question behind which was how to pass arguments to annotation processors.




        Compiler arguments can be specified with -A flag.



        In Gradle:



        compileJava.options.compilerArgs += "-Agraphdep.project=$project.name"


        In Maven:



        <compilerArgs>
        <arg>-Agraphdep.project=$project.artifactId</arg>
        </compilerArgs>


        Then from within an implementation of AbstractProcessor it is possible to retrieve the arguments using:



        processingEnv.getOptions().get("widget");


        The options supported must be declared by the processor, either by using the annotation @SupportedOptions("widget") or by overriding the method public Set<String> getSupportedOptions().







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Nov 13 '18 at 6:10









        GauthierGauthier

        2,3071822




        2,3071822



























            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.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53259684%2fmaven-gradle-set-environment-variable-for-compilation%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

            Use pre created SQLite database for Android project in kotlin

            Darth Vader #20

            Ondo