i have 4 projects, have several modules in common.
when try run sonarqube complete analysis, first project gets analyzed. starting second project, error message along lines of "xxx module present in server".
each of 4 projects contains aggregator pom. use build them , run maven sonar:sonar goal.
what best approach solve issue?
it seems you're breaking component/module/library conventions or mis used it. configuration management principles you're not supposed "include" (build in case of binary configuration management) component multiple times.
having library have many other ones depends on , last ones independant dependancy have manage appart other framework.
you're supposed install/deploy component on own , refer it. same principles apply on sonarqube configuration manager. can't have shared components analyzed through different "products".
they must have own life cycle. how manage evolution of shared librairies when having 4 projects living in parallel of each others ?
Comments
Post a Comment