This makes sense up to the point where you'd like outside
contributors to
provide a fix to an existing plugin. If we had the plugin master
depend on the
core SNAPSHOT version, we'd essentially force the outside contributor
to build
everything from source to be able to test their contribution - as you
correctly point out. But fixes to the existing plugins is what I
think we need
most from the community and therefore exactly this workflow should be
made as
easy as possible.
Couldn't we just override the dependencies to the published artifacts by dependencies
to the SNAPSHOT versions by including this into the maven dev profile? This would allow us
to not publish every little change in core, because we are using the dev profile while
building the modules and at the same time, the default behavior would enforce the
dependency on published mvn artifacts.
This approach needs some refactoring -> to use the dependency management or even BOM
files would be nice for it. What do you think?
http://mavenize.blogspot.cz/2007/06/profiles-dependency-management.html
jk