JVM and Intellij uses the avro generated classes, not imported ones












0















While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as



"name": "ruleKey",
"type": [
"null",
{
"type": "enum",
"name": “Rule”,
"namespace": "com.testing.common.rules.api",
"symbols": [
"MIN_AGE",
“MAX_AGE”
]
}
]


, and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.

The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.










share|improve this question





























    0















    While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as



    "name": "ruleKey",
    "type": [
    "null",
    {
    "type": "enum",
    "name": “Rule”,
    "namespace": "com.testing.common.rules.api",
    "symbols": [
    "MIN_AGE",
    “MAX_AGE”
    ]
    }
    ]


    , and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.

    The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.










    share|improve this question



























      0












      0








      0








      While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as



      "name": "ruleKey",
      "type": [
      "null",
      {
      "type": "enum",
      "name": “Rule”,
      "namespace": "com.testing.common.rules.api",
      "symbols": [
      "MIN_AGE",
      “MAX_AGE”
      ]
      }
      ]


      , and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.

      The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.










      share|improve this question
















      While generating java code from Avro scheme using commerce hub Gradle plugin, it takes the object which has a field such as



      "name": "ruleKey",
      "type": [
      "null",
      {
      "type": "enum",
      "name": “Rule”,
      "namespace": "com.testing.common.rules.api",
      "symbols": [
      "MIN_AGE",
      “MAX_AGE”
      ]
      }
      ]


      , and generates Java class from the scheme, including enum fields such as Rule. In the same time, I am importing common rules(com.testing.common.rules.api) and it imports Rule as well. I would like to use methods from the common library, however, Avro generated model has a higher priority. ( The Java interpreter will look for classes in the directories in the order they appear in the classpath variable. In this case, the ones generated from the scheme) and it doesn’t let me use the imported class from the common library, because Avro already generated Rule enum class with the same package and name.

      The used technologies are spring boot 2, Java 10 and commercehub.gradle plugin.







      java spring spring-boot serialization avro






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 '18 at 10:11







      Etibar Hasanov

















      asked Nov 20 '18 at 8:36









      Etibar HasanovEtibar Hasanov

      9712721




      9712721
























          2 Answers
          2






          active

          oldest

          votes


















          0














          IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.






          share|improve this answer































            0














            Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.



            And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.



            Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).






            share|improve this answer
























            • Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

              – Etibar Hasanov
              Nov 20 '18 at 10:30













            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%2f53389044%2fjvm-and-intellij-uses-the-avro-generated-classes-not-imported-ones%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.






            share|improve this answer




























              0














              IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.






              share|improve this answer


























                0












                0








                0







                IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.






                share|improve this answer













                IDEA honors class path ordering. First match wins ( as you already found out ) - so you have to reorder classpath elements in your project / module classpath setting.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 20 '18 at 10:15









                Konstantin PribludaKonstantin Pribluda

                11k12133




                11k12133

























                    0














                    Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.



                    And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.



                    Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).






                    share|improve this answer
























                    • Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                      – Etibar Hasanov
                      Nov 20 '18 at 10:30


















                    0














                    Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.



                    And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.



                    Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).






                    share|improve this answer
























                    • Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                      – Etibar Hasanov
                      Nov 20 '18 at 10:30
















                    0












                    0








                    0







                    Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.



                    And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.



                    Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).






                    share|improve this answer













                    Actually, none of the things you listed in your question really matter. As in: you have two classes x.y.Z, with the same name, and the package.



                    And that doesn't work. When you import x.y.Z, the JVM starts searching the class path, and will pick the first class it find. And there is nothing you can do about that.



                    Thus, the only solution: make sure that your class path only contains the class you intend to use. This is also a good preparation for the future, as Java9 will not allow you to have two modules with conflicting x.y.Z classes (in the same layer).







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered Nov 20 '18 at 10:20









                    GhostCatGhostCat

                    89.2k1687146




                    89.2k1687146













                    • Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                      – Etibar Hasanov
                      Nov 20 '18 at 10:30





















                    • Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                      – Etibar Hasanov
                      Nov 20 '18 at 10:30



















                    Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                    – Etibar Hasanov
                    Nov 20 '18 at 10:30







                    Actually, I didn't say out one part, in my case field Rule comes from a common library . Rule is a field in the scheme and in the same time it is imported by the project. When we generate java code from the scheme, then JVM understands it as two classes with the same name, and the package. However, it is basically the same, one generated from Avro scheme, another one imported from the common library. If there was a way to 'tell' avro plugin not generate the field, use existing ones, it would solve the issue.

                    – Etibar Hasanov
                    Nov 20 '18 at 10:30




















                    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%2f53389044%2fjvm-and-intellij-uses-the-avro-generated-classes-not-imported-ones%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

                    android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

                    SQL update select statement

                    'app-layout' is not a known element: how to share Component with different Modules