<!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="https://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;">
Tagging/branching of JBoss Tools Core subcomponents
</h3>
<span style="margin-bottom: 10px;">
created by <a href="https://community.jboss.org/people/maxandersen">Max Rydahl Andersen</a> in <i>JBoss Tools</i> - <a href="https://community.jboss.org/docs/DOC-48350">View the full document</a>
</span>
<hr style="margin: 20px 0; border: none; background-color: #dadada; height: 1px;">
<div class="jive-rendered-content"><p>Our recent move to git caused some confusion on how we tag/branch components in JBoss Tools core components.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1>Current versioning</h1><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>To avoid future confusion here are the short version of the current approach:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><ol><li>Each component has its own version in manifest.mf/pom.xml</li><li>The git repositories should use tag/branches based on jbosstools version (jbosstools-<version>x for branches, jbosstools-<version> for tag)</li><li>In Jira use the jbosstools version for reporting/targeting issues.</li></ol><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>The advantage of the above is that git & jira use the same version and no need to juggle multiple versions for git nor for jira queries.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>i.e. with a unified tag like "jbosstools-4.1.0.Alpha1" you can find which version is used of a specific component for a specific jboss tools release easily.</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><h1><span style="font-size: 18pt;">Future Versioning</span></h1><p>The disadvantage of the above is i<span style="font-size: 10pt;">t assumes components are always released/rebuilt for each JBoss Tools release.</span></p><p><span style="font-size: 10pt;">This is something we would like to move away from requiring to allow for smaller updates (only download what actually changed) and</span></p><p><span style="font-size: 10pt;">faster build times (aggregation is faster than always build from source).</span></p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>What we need to get to a model where:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><ol><li>Each component has its own version in manifest.mf/pom.xml</li><li>The git repositories should use tag/branches based on component version </li></ol><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><p>Is to solve (or ignore <span> ;) </span> following issues:</p><p style="min-height: 8pt; height: 8pt; padding: 0px;"> </p><ul><li>Jira ?<ul><li>jira does not have support for versions per component, thus need project per component.<ul><li>How to get query to see which issues are missing/left ?</li></ul></li></ul></li><li>Git<ul><li>how to know which version is included in jboss tools release ?<ul><li>can we use submodules to model this ?</li><li>use eclipse's map file approach ?</li><li>Something else ?</li><li></li></ul></li></ul></li></ul></div>
<div style="background-color: #f4f4f4; padding: 10px; margin-top: 20px;">
<p style="margin: 0;">Comment by <a href="https://community.jboss.org/docs/DOC-48350">going to Community</a></p>
<p style="margin: 0;">Create a new document in JBoss Tools at <a href="https://community.jboss.org/choose-container!input.jspa?contentType=102&containerType=14&container=2128">Community</a></p>
</div></td>
</tr>
</tbody>
</table>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>