Ah... right. OK, I see. So yeah, if you have actual CODE in the parent, then that I
believe will screw things up.
That might be why the jboss integration parent and bom do not have any code in them. They
are very small.
I'm inclined to follow the pattern they use - since they are actually using it and
probably did it like that for a reason(s).
The parent, as I say earlier, provides other things like pluginManagement, repositories,
and other things the children can pick up for free.
But if there is glue code in there, that seems wrong. The parent should be concerned with
maven things only (not, say, for building a java jar).
----- Original Message -----
On 2014-11-21 17:27, Heiko W.Rupp wrote:
>
>> 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.
>
> I thought it would be best to have overall bom + integration in one repo.
> If I do "mvn install" we would get the alohomora "product" built
by pulling
> in the code from the dependencies and so on.
>
> If that does not work as one repo, so be it.
alhomora-bom maven project cannot be a maven child of alhomora-parent
(if alhomora-parent is supposed to contain the glue code) and should
also have a release cycle separate from alhomora-parent.
alhomora-bom can theoretically stay in alohomora git repo, but it would
be impractical - think of having the independent tags of alhomora-bom
and alhomora-parent in the same git repo...
I vote for moving alhomora-bom to alhomora-bom repo.
-- P
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-devel