Hi John, inline...
On 2014-11-21 17:05, John Mazzitelli wrote:
> I am afraid, the present setup, as explained on IRC, does not
work. I
> tried to implement a subproject sub1 in a separate project and I added
> some glue code under alhomora-parent. It contains a kind of a dependency
> cycle - i.e. none of alhomora-parent or alhomora-sub1 can be built.
I copied the pattern from that jboss intergration project, no? I think that is how they
did it. They had a parent with the bom under it.
You can either depend on the bom only (if you are completely separate) or you can have
your module have the parent as its parent, and then depend on the bom. This pulls in the
version sysprops for you as well as having the repositority and pluginManagement
definitions. If you do NOT have the parent as your parent, you don't get the sysprops,
repos, or plugin definitions - you only get dependencies.
See here:
https://github.com/jboss-integration/jboss-integration-platform-bom
There is a root pom, then ip-bom/pom.xml is the bom module.
That's the pattern jmazzitelli/alohomora used.
I prototyped its use in rhq-msg (soon to be renamed :) - here:
https://github.com/rhq-project/rhq-msg/blob/mazz/use-bom/pom.xml
Yes, this is a useful example but it is missing how rhq-msg is supposed
to be used/integrated/glued. Heiko said on irc that the glue code is
supposed to live under alhomora-parent. Adding it there (cf.
https://github.com/ppalaga/alohomora/tree/141121-dep-cycle/alohomora-glue)
would introduce a cycle in your example too, would it not?
-- P