@jdubois To make my thinking more concrete, here's a proposal to put the jhipster serverside library and jhipster-dependencies in a single repository, with all plugin configuration managed in the same place.
This would resolve the co-dependency issue I mentioned here.
I've verified that maven-release-plugin, when running mvn release:prepare
from the top directory, correctly replaces all the right version properties, so I would expect mvn release:perform
to work well and release all three artifacts simultaneously.
Also, Travis works because it just hands off to the maven reactor, which builds the modules in the appropriate order -- and so Travis would fail if Maven fails.
But I noticed that the server-side library doesn't have any unit tests? This means that surefire and jacoco don't actually do anything at the moment... This is already the case on current master, though, so unrelated to this PR.
For what it's worth, I think it'd be all right to consider something like this change independently of the moment at which you would like to move generator-jhipster to use the new BOM.
Finally, if we would like to add some "steroids" like @Tcharl suggested, we would now have quite a natural place to do that.