jira-importer commented on issue #703: URL: https://github.com/apache/maven-javadoc-plugin/issues/703#issuecomment-2957347069
**[Vincent Zurczak](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=vzurczak)** commented Well, considering the alternative is not better. I have 3 Git repositories, each one defining a release group. It means I release all the Maven modules that are in a source repository. This is because you can only tag an entire Git repository, unlike SVN (this has pros and cons). So, I have one repository for my parent. One for my main project (platform). And one for a related project (tooling). What I wanted to do is to define common quality rules for my platform and tooling projects. The overall idea would be to define them in the parent. But this results in circular dependencies if my parent depends on one of its children (egg and chicken story). And if I simply make my _build-tools_ module not a child of the parent, then the **maven-release-plugin** does not release correctly. So, I would need a fourth Git repository to host my quality project (CSS stylesheet for the Javadoc, and resources for Checkstyle). Seriously, I don't like this. Putting these resources on a web server makes everything simple. One single parent, that references static resources. I have the control over this web server. With the **maven-checstyle-plugin**, if the web server is offline, the build will fail. And with the **maven-javadoc-plugin**, if the web server is offline, the default CSS will be used (which is totally acceptable for snapshots, and most unlikely to happen for releases). I think this kind of feature is really helpful for multi-module projects. And in particular when they are hosted on Git repositories. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
