You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The multi-module Maven project was much harder to maintain (all those plug-ins and bugs due to the nature of the project, site generation, having issues releasing to Sonatype, etc).
The current master has a single module project, but I found one issue where a user is reporting problems with JUnit integration.
So perhaps a multi-module would be necessary. A single module with all the dependencies is bad as it would bring those dependencies to all projects (keeping it Java 8 as well). So perhaps a multi-module is still necessary 😕
The text was updated successfully, but these errors were encountered:
The multi-module Maven project was much harder to maintain (all those plug-ins and bugs due to the nature of the project, site generation, having issues releasing to Sonatype, etc).
The current master has a single module project, but I found one issue where a user is reporting problems with JUnit integration.
So perhaps a multi-module would be necessary. A single module with all the dependencies is bad as it would bring those dependencies to all projects (keeping it Java 8 as well). So perhaps a multi-module is still necessary 😕
The text was updated successfully, but these errors were encountered: