<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<html>
<body link="#355491" alink="#4262a1" vlink="#355491" style="background: #e2e2e2; margin: 0; padding: 20px;">
<div>
<table cellpadding="0" bgcolor="#FFFFFF" border="0" cellspacing="0" style="border: 1px solid #dadada; margin-bottom: 30px; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td>
<table border="0" cellpadding="0" cellspacing="0" bgcolor="#FFFFFF" style="border: solid 2px #ccc; background: #dadada; width: 100%; -moz-border-radius: 6px; -webkit-border-radius: 6px;">
<tbody>
<tr>
<td bgcolor="#000000" valign="middle" height="58px" style="border-bottom: 1px solid #ccc; padding: 20px; -moz-border-radius-topleft: 3px; -moz-border-radius-topright: 3px; -webkit-border-top-right-radius: 5px; -webkit-border-top-left-radius: 5px;">
<h1 style="color: #333333; font: bold 22px Arial, Helvetica, sans-serif; margin: 0; display: block !important;">
<!-- To have a header image/logo replace the name below with your img tag -->
<!-- Email clients will render the images when the message is read so any image -->
<!-- must be made available on a public server, so that all recipients can load the image. -->
<a href="http://community.jboss.org/index.jspa" style="text-decoration: none; color: #E1E1E1">JBoss Community</a></h1>
</td>
</tr>
<tr>
<td bgcolor="#FFFFFF" style="font: normal 12px Arial, Helvetica, sans-serif; color:#333333; padding: 20px; -moz-border-radius-bottomleft: 4px; -moz-border-radius-bottomright: 4px; -webkit-border-bottom-right-radius: 5px; -webkit-border-bottom-left-radius: 5px;"><h3 style="margin: 10px 0 5px; font-size: 17px; font-weight: normal;">
Coping with versions in large multi-module osgi projects
</h3>
<span style="margin-bottom: 10px;">
new comment by <a href="http://community.jboss.org/people/maxandersen">Max Rydahl Andersen</a> - <a href="http://community.jboss.org/community/tools/blog/2011/09/17/coping-with-versions-in-large-multi-module-osgi-projects#comment-7627">View all comments on this blog post</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Ian, </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>regarding PDE/Build - Tycho does the exact same thing with 1.0.0.qualifier - this is no different at all, the same version is never reused for the same bundle for releases. </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>regarding "If <strong style="font-size: 12px; font-family: 'Lucida Sans', 'Lucida Sans Unicode', 'Lucida Grande', Verdana, Arial, Helvetica, sans-serif;">nothing</strong> changes in a bundle then the version should not change", I agree that is the optimal goal but as you just wrote .qualifier gets changed anyway by the build so this actually happens anyway if you dont remove the .qualifier. And please note, I'm not saying we are putting the same version on all 628 artifacts - just setting one version per module (so 628 becomes 42 instead which )</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>"Eclipse project has 400 bundles and they manage their versions without bumping each bundle for each build" - that is not what im seeing, they have .qualifier too. Anyway, Eclipse project also have a good deal of more people to handle these versions. That is another approach we could take, reduce the number of modules and version them individually but the end result would be similar... smaller set of managable artifacts all released at the same time - but now you can install smaller parts <span> :) </span> </p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>note, map files is actually the key part missing in Tycho/maven workflow to avoid full rebuilds at release builds IMO, but that does not solve the problems for continous integration builds.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>I know about jar.comparator/API Tools (which btw. is pretty good but *awfully* slow and tricky to get setup all across modules without either having PDE or Tycho die in the process ;( - and even if we had it up and running it would just help about detecting the needed version bumps and there would still need to be a step that goes through and ensures pom.xml, manifest.mf, feature's, etc. are in sync.</p></div>
</td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>