Multi-Module dependencies and generated code pathing issue

We have an application that is broken into many modules on many layers, included code generation.

I am trying to set up my project, but always seem to have to set my classpath to the jars that store the .class files of the generated code, instead of getting it directly from the .java generated files, which are in my dependency list for those modules that need them.

Without the jars I am getting lost of red on the right side. I shouldn't have to point to the jars, it should use the dependency to the module I created that points to the generated code.

Anyone have any ideas? or IntelliJ IDEAs.

Thanks

Mark

3 comments
Comment actions Permalink

Hmm, no responses for such a simple question? Doesn't bode well.

Mark

0
Comment actions Permalink

You should have module B dependant on Module A. Make sure that Module A
comes before any library that may also have the Module A classes. This
will allow you to compile and navigate to/from the sources.

Mark Spritzler wrote:

>We have an application that is broken into many modules on many layers, included code generation.
>
>I am trying to set up my project, but always seem to have to set my classpath to the jars that store the .class files of the generated code, instead of getting it directly from the .java generated files, which are in my dependency list for those modules that need them.
>
>Without the jars I am getting lost of red on the right side. I shouldn't have to point to the jars, it should use the dependency to the module I created that points to the generated code.
>
>Anyone have any ideas? or IntelliJ IDEAs.
>
>Thanks
>
>Mark

>

0
Comment actions Permalink

Thanks, I'll look into that, but I am pretty sure that I specifically put all the libraries at the end, but I have been known to make mistakes many, if not all the time. :)

Mark

0

Please sign in to leave a comment.