I don't think this really works, does it? As soon as some dev makes
changes to plugins/master/pluginX that depends on core/master's snapshot
version, the non-dev profile that depends on core/release will not
build. maybe I am confused.
On 3/14/2013 12:11 PM, Jiri Kremser wrote:
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
_______________________________________________ rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel