sbt plugin - How to make sure my settingKey is resolve before everything else?












0















I have a settingKey[Level.Value] which is for the level of logs. I would like to set this value prior to everything else so that my log level is applied to everything.



( I know there is a setLogLevel but I would like to be able to set it, only for my Plugin )



If my setting is named myLogLevel, I tried to call myLogLevel.value inside each of my tasks and settings.



The issue seems to be that if I am not using the value yield by it, then the setting is not executed.



My setting is something like that :



myLogLevel := {
val theValueSetByTheUser = myLogLevel.value
MyLogLibrary.setLevel(theValueSetByTheUser)
theValueSetByTheUser
}


So what should I do ? Should I call println(myResultLevel) everywhere so it is used. It seems silly.



Thank you.










share|improve this question



























    0















    I have a settingKey[Level.Value] which is for the level of logs. I would like to set this value prior to everything else so that my log level is applied to everything.



    ( I know there is a setLogLevel but I would like to be able to set it, only for my Plugin )



    If my setting is named myLogLevel, I tried to call myLogLevel.value inside each of my tasks and settings.



    The issue seems to be that if I am not using the value yield by it, then the setting is not executed.



    My setting is something like that :



    myLogLevel := {
    val theValueSetByTheUser = myLogLevel.value
    MyLogLibrary.setLevel(theValueSetByTheUser)
    theValueSetByTheUser
    }


    So what should I do ? Should I call println(myResultLevel) everywhere so it is used. It seems silly.



    Thank you.










    share|improve this question

























      0












      0








      0








      I have a settingKey[Level.Value] which is for the level of logs. I would like to set this value prior to everything else so that my log level is applied to everything.



      ( I know there is a setLogLevel but I would like to be able to set it, only for my Plugin )



      If my setting is named myLogLevel, I tried to call myLogLevel.value inside each of my tasks and settings.



      The issue seems to be that if I am not using the value yield by it, then the setting is not executed.



      My setting is something like that :



      myLogLevel := {
      val theValueSetByTheUser = myLogLevel.value
      MyLogLibrary.setLevel(theValueSetByTheUser)
      theValueSetByTheUser
      }


      So what should I do ? Should I call println(myResultLevel) everywhere so it is used. It seems silly.



      Thank you.










      share|improve this question














      I have a settingKey[Level.Value] which is for the level of logs. I would like to set this value prior to everything else so that my log level is applied to everything.



      ( I know there is a setLogLevel but I would like to be able to set it, only for my Plugin )



      If my setting is named myLogLevel, I tried to call myLogLevel.value inside each of my tasks and settings.



      The issue seems to be that if I am not using the value yield by it, then the setting is not executed.



      My setting is something like that :



      myLogLevel := {
      val theValueSetByTheUser = myLogLevel.value
      MyLogLibrary.setLevel(theValueSetByTheUser)
      theValueSetByTheUser
      }


      So what should I do ? Should I call println(myResultLevel) everywhere so it is used. It seems silly.



      Thank you.







      scala sbt






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 19 '18 at 22:29









      WonayWonay

      392111




      392111
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I found a solution :



          You need two settingKey.



          The first one is : myLogLevel: settingKey[Level.Value] .



          And consumer of your plugin can set it to whatever in their build.sbt and you can put a default value in your settings: myLogLevel := Level.Info .



          Then, you have a second setting: myLog: settingKey[Logger]



          which is not exposed to the consumer and you define it like :



          myLog := {
          createLogOfLevel(myLogLevel.value)
          }


          And in your other task and setting, you can now call:



          val log = myLog.value
          log.info("message")





          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%2f53383575%2fsbt-plugin-how-to-make-sure-my-settingkey-is-resolve-before-everything-else%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














            I found a solution :



            You need two settingKey.



            The first one is : myLogLevel: settingKey[Level.Value] .



            And consumer of your plugin can set it to whatever in their build.sbt and you can put a default value in your settings: myLogLevel := Level.Info .



            Then, you have a second setting: myLog: settingKey[Logger]



            which is not exposed to the consumer and you define it like :



            myLog := {
            createLogOfLevel(myLogLevel.value)
            }


            And in your other task and setting, you can now call:



            val log = myLog.value
            log.info("message")





            share|improve this answer




























              0














              I found a solution :



              You need two settingKey.



              The first one is : myLogLevel: settingKey[Level.Value] .



              And consumer of your plugin can set it to whatever in their build.sbt and you can put a default value in your settings: myLogLevel := Level.Info .



              Then, you have a second setting: myLog: settingKey[Logger]



              which is not exposed to the consumer and you define it like :



              myLog := {
              createLogOfLevel(myLogLevel.value)
              }


              And in your other task and setting, you can now call:



              val log = myLog.value
              log.info("message")





              share|improve this answer


























                0












                0








                0







                I found a solution :



                You need two settingKey.



                The first one is : myLogLevel: settingKey[Level.Value] .



                And consumer of your plugin can set it to whatever in their build.sbt and you can put a default value in your settings: myLogLevel := Level.Info .



                Then, you have a second setting: myLog: settingKey[Logger]



                which is not exposed to the consumer and you define it like :



                myLog := {
                createLogOfLevel(myLogLevel.value)
                }


                And in your other task and setting, you can now call:



                val log = myLog.value
                log.info("message")





                share|improve this answer













                I found a solution :



                You need two settingKey.



                The first one is : myLogLevel: settingKey[Level.Value] .



                And consumer of your plugin can set it to whatever in their build.sbt and you can put a default value in your settings: myLogLevel := Level.Info .



                Then, you have a second setting: myLog: settingKey[Logger]



                which is not exposed to the consumer and you define it like :



                myLog := {
                createLogOfLevel(myLogLevel.value)
                }


                And in your other task and setting, you can now call:



                val log = myLog.value
                log.info("message")






                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 19 '18 at 22:40









                WonayWonay

                392111




                392111






























                    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%2f53383575%2fsbt-plugin-how-to-make-sure-my-settingkey-is-resolve-before-everything-else%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

                    MongoDB - Not Authorized To Execute Command

                    in spring boot 2.1 many test slices are not allowed anymore due to multiple @BootstrapWith

                    Npm cannot find a required file even through it is in the searched directory