This is a link to the FSW related integration bom:
https://github.com/jboss-integration/jboss-integration-platform-bom
The top level readme contains a description of the aims, but regarding local overrides,
one aim was to update the bom to the most recent version required by any of the
sub-projects - so sometimes if this would cause a sub-project an issue, that project would
use a local override until it had a chance to align with the new version.
So not sure we should disallow it, but obviously we need to minimise the local overrides
as much as possible.
Regards
Gary
----- Original Message -----
Hello,
RHQ.next is / will be split and developed in several sub-projects on their
own like rhq-metrics, rhq-msg, rhq-audit and so on.
This also means that we need a "central place" to integrate all the pieces
into one.
In addition we need to make sure that the sub-projects use "compatible"
versions of dependencies.
So I propose that we introduce a rhq.next project (*) that servers those two
purposes
- integration of individual project
- master pom/bom for versions of dependencies
During the initial development cycle, we may need to publish that bom more
often in order to
make dependency definitions available, but should be better off in the long
run.
I don't know if there is a way to enforce that the individual projects don't
just override the settings from the bom.
I know there are people on the list, that have done that before and can
probably help with the setup.
Heiko
*) or branch inside "rhq" project if we want to keep that name
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschäftsführer: Charles Cachera, Michael Cunningham, Paul Hickey, Charlie
Peters
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel