Eclipse The hierarchy of type VerificationTokenRepository is inconsistent












0















I have the following project structure:



P - Parent Module
A - Module A with parent P
B - Module B with parent P and depends on A (no module-info)


In module A I have the following interfaces:



public interface IRepository<T, K extends Serializable> extends JpaRepository<T, K>
public interface IIdRepository<T> extends IRepository<T, Long> {/* */}
public interface ITokenRepository<T extends AbstractToken> extends IIdRepository<T>


and in Module B I have the following interface:



public interface VerificationTokenRepository<T extends VerificationToken> extends ITokenRepository<T>{


This last interface is the one that gets the subject message. None of the interfaces in Module A cause any errors. All the dependencies in the pom for Module A exist in the pom for Module B and Module B has Module A as a dependency. If I change the definition fo VerificationTokenRegistry so that it extends each of the other interfaces, I still get the same error. If it extends JpaRepository I get no error. I have cleaned, installed, and deployed each of the dependencies. I have restarted Eclipse. But that doesn't help.



Additionally, the error occurs only in the editor window. It does not appear in the Problem window, the Marker window and is not flagged in the Package Explorer window.



The error occurs in the same way for all the interfaces defined in Module B which extend interfaces in Module A.










share|improve this question



























    0















    I have the following project structure:



    P - Parent Module
    A - Module A with parent P
    B - Module B with parent P and depends on A (no module-info)


    In module A I have the following interfaces:



    public interface IRepository<T, K extends Serializable> extends JpaRepository<T, K>
    public interface IIdRepository<T> extends IRepository<T, Long> {/* */}
    public interface ITokenRepository<T extends AbstractToken> extends IIdRepository<T>


    and in Module B I have the following interface:



    public interface VerificationTokenRepository<T extends VerificationToken> extends ITokenRepository<T>{


    This last interface is the one that gets the subject message. None of the interfaces in Module A cause any errors. All the dependencies in the pom for Module A exist in the pom for Module B and Module B has Module A as a dependency. If I change the definition fo VerificationTokenRegistry so that it extends each of the other interfaces, I still get the same error. If it extends JpaRepository I get no error. I have cleaned, installed, and deployed each of the dependencies. I have restarted Eclipse. But that doesn't help.



    Additionally, the error occurs only in the editor window. It does not appear in the Problem window, the Marker window and is not flagged in the Package Explorer window.



    The error occurs in the same way for all the interfaces defined in Module B which extend interfaces in Module A.










    share|improve this question

























      0












      0








      0








      I have the following project structure:



      P - Parent Module
      A - Module A with parent P
      B - Module B with parent P and depends on A (no module-info)


      In module A I have the following interfaces:



      public interface IRepository<T, K extends Serializable> extends JpaRepository<T, K>
      public interface IIdRepository<T> extends IRepository<T, Long> {/* */}
      public interface ITokenRepository<T extends AbstractToken> extends IIdRepository<T>


      and in Module B I have the following interface:



      public interface VerificationTokenRepository<T extends VerificationToken> extends ITokenRepository<T>{


      This last interface is the one that gets the subject message. None of the interfaces in Module A cause any errors. All the dependencies in the pom for Module A exist in the pom for Module B and Module B has Module A as a dependency. If I change the definition fo VerificationTokenRegistry so that it extends each of the other interfaces, I still get the same error. If it extends JpaRepository I get no error. I have cleaned, installed, and deployed each of the dependencies. I have restarted Eclipse. But that doesn't help.



      Additionally, the error occurs only in the editor window. It does not appear in the Problem window, the Marker window and is not flagged in the Package Explorer window.



      The error occurs in the same way for all the interfaces defined in Module B which extend interfaces in Module A.










      share|improve this question














      I have the following project structure:



      P - Parent Module
      A - Module A with parent P
      B - Module B with parent P and depends on A (no module-info)


      In module A I have the following interfaces:



      public interface IRepository<T, K extends Serializable> extends JpaRepository<T, K>
      public interface IIdRepository<T> extends IRepository<T, Long> {/* */}
      public interface ITokenRepository<T extends AbstractToken> extends IIdRepository<T>


      and in Module B I have the following interface:



      public interface VerificationTokenRepository<T extends VerificationToken> extends ITokenRepository<T>{


      This last interface is the one that gets the subject message. None of the interfaces in Module A cause any errors. All the dependencies in the pom for Module A exist in the pom for Module B and Module B has Module A as a dependency. If I change the definition fo VerificationTokenRegistry so that it extends each of the other interfaces, I still get the same error. If it extends JpaRepository I get no error. I have cleaned, installed, and deployed each of the dependencies. I have restarted Eclipse. But that doesn't help.



      Additionally, the error occurs only in the editor window. It does not appear in the Problem window, the Marker window and is not flagged in the Package Explorer window.



      The error occurs in the same way for all the interfaces defined in Module B which extend interfaces in Module A.







      java eclipse






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Dec 21 '18 at 3:53









      AixNPanesAixNPanes

      4981715




      4981715
























          1 Answer
          1






          active

          oldest

          votes


















          0














          I found that one way to bypass the problem is to separate the offending code into a separate module. The validation module doesn't seem to have a problem if that is done. I assume that is because the amount of code in the module is small.






          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%2f53878950%2feclipse-the-hierarchy-of-type-verificationtokenrepository-is-inconsistent%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 that one way to bypass the problem is to separate the offending code into a separate module. The validation module doesn't seem to have a problem if that is done. I assume that is because the amount of code in the module is small.






            share|improve this answer




























              0














              I found that one way to bypass the problem is to separate the offending code into a separate module. The validation module doesn't seem to have a problem if that is done. I assume that is because the amount of code in the module is small.






              share|improve this answer


























                0












                0








                0







                I found that one way to bypass the problem is to separate the offending code into a separate module. The validation module doesn't seem to have a problem if that is done. I assume that is because the amount of code in the module is small.






                share|improve this answer













                I found that one way to bypass the problem is to separate the offending code into a separate module. The validation module doesn't seem to have a problem if that is done. I assume that is because the amount of code in the module is small.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Jan 19 at 3:12









                AixNPanesAixNPanes

                4981715




                4981715






























                    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%2f53878950%2feclipse-the-hierarchy-of-type-verificationtokenrepository-is-inconsistent%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

                    Liquibase includeAll doesn't find base path

                    How to use setInterval in EJS file?

                    Petrus Granier-Deferre