<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=ISO-8859-1">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi,<br>
there are currently two Maven pom files in Infinispan where
dependency versions are defined - infinispan-bom and
infinispan-parent. For instance, version.protostream is defined in
the BOM while version.commons.pool is defined in infinispan-parent.<br>
<br>
This causes me troubles when I want to do filtering with
maven-resources-plugin and substitute versions of dependencies in
certain configuration file because properties defined in the BOM are
not visible to other modules (I'm currently trying to generate
"features" file for HotRod to be easily deployable into Karaf -
<a class="moz-txt-link-freetext" href="https://issues.jboss.org/browse/ISPN-3967">https://issues.jboss.org/browse/ISPN-3967</a>, and I can't really access
versions of some dependencies)<br>
<br>
We include the BOM file in infinispan-parent as a dependency with
scope "import" which causes the properties defined in the BOM to be
lost. <br>
<br>
Questions:<br>
Is there a reason why we include it as a dependency and do not have
it as a parent of infinispan-parent? (as suggested in [1])<br>
Can someone explain the reason why we have version declarations in
two separate files?<br>
If you possibly know how to access properties in the BOM, please
advise. To me it seems impossible without some nasty hacks.<br>
<br>
Thanks,<br>
Martin<br>
<br>
<br>
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html">[1]
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html</a><br>
</body>
</html>