java - Circular dependencies or right way to build a project -
java - Circular dependencies or right way to build a project -
i have project web-app.
most classes of project must compiled .jar file , set server codebase/web-inf/lib dir. these classes used server only.
but have classes need used on server , client. these classes must set straight codebase/[package.class].
all of these classes depend on each other , vice-versa.
end of story. seek move project ide build gradle. project contains 2 modules depend on each other. inteljid provide warning me , compile fine. gradle gets stuck. so, can somehow split these classes in 2 logical groups, , have easy way build construction described above?
i trying create multi-project build, several sourcesets everywhere got same circular dependency errors.
you need refactor code. 1 way of doing create separate project server specific code, project client project , mutual project code needs shared. next, can allow server project , client project depend on mutual project. however, there should not dependencies between server project , client project themselves.
typically, maintain mutual project little possible. inquire if class necessary in both projects? if not, should not part of mutual package. create sure maintain dependencies between classes, packages , projects unidirectional. may include quite lot of refactoring since code tangled.
recommended reading:
clean code "uncle bob" martin working legacy code michael feathers java gradle project
Comments
Post a Comment