java - Best ivy practice: Split code into multiple projects or use one project with multiple configurations? -
at work have number of projects need share common code. code universal while of code shared subset of our projects. should split common code 2 separate projects or use 2 different ivy configurations single project?
option 1 - 2 separate projects.
- proj 1 - common published default configuration
- proj 1 - common-xml published default configuration
potential issues: requires have 2 separate projects, 2 separate build files , 2 separate ivy files.
option 2 - 1 project, multiple ivy configurations different artifacts
- artifact 1 - common published core
- artifact 2 - common xml published core-xml
potential issues: may have maintain separate source directories in same project.
in either case, common xml component may rely on common core component.
so, sf, should maintaining common code? issues did miss 2 methods, , other pros/cons or alternative solutions?
hmm, comes down how prefer manage source code. first, i'd asking question of whether need split source. idea of commons project encapsulate code, classes, interfaces, etc can used common toolkit other projects. doesn't mean projects have use in commons. might use small portion of it. that's fine , might splitting commons on optimisation.
think of - happens if next project uses different subset of commons library? going split again?
Comments
Post a Comment