<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Hmm, actually I think I’m to blame in this case because I did the release without properly thinking about the version numbers.<div>If you could point me to packages that are hit by the imglib-algorithm change, I’ll try to fix them.</div><div>best regards,</div><div>Tobias</div><div><br><div><div>On 16 Mar 2015, at 21:58, <<a href="mailto:tinevez@pasteur.fr">tinevez@pasteur.fr</a>> <<a href="mailto:tinevez@pasteur.fr">tinevez@pasteur.fr</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr" style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;"><div data-externalstyle="false" dir="ltr" style="font-family: Calibri, 'Segoe UI', Meiryo, 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', sans-serif; font-size: 12pt;"><div style="">Fudge fudge fudge I did this.</div><div style="">I am really sorry this is something I vastly overlooked.<span class="Apple-converted-space"> </span><br></div><div data-signatureblock="true" style=""><div style="">Next pizza & beer are on me.</div><div style=""><br></div></div><div style="padding-top: 5px; border-top-color: rgb(229, 229, 229); border-top-width: 1px; border-top-style: solid;"><font face=" 'Calibri', 'Segoe UI', 'Meiryo', 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', 'sans-serif'" style="line-height: 15pt; letter-spacing: 0.02em; font-family: Calibri, 'Segoe UI', Meiryo, 'Microsoft YaHei UI', 'Microsoft JhengHei UI', 'Malgun Gothic', sans-serif; font-size: 12pt;"><b>De :</b> <a href="mailto:hiner@wisc.edu" target="_parent">Mark Hiner</a><br><b>Envoyé :</b> lundi 16 mars 2015 20:38<br><b>À :</b> <a href="mailto:pietzsch@mpi-cbg.de" target="_parent">Tobias Pietzsch</a>,<span class="Apple-converted-space"> </span><a href="mailto:tinevez@pasteur.fr" target="_parent">Jean-Yves Tinevez</a><br><b>Cc :</b> <a href="mailto:imagej-devel@imagej.net" target="_parent">imagej-devel@imagej.net</a></font></div><div><br></div><div dir=""><div dir="ltr"><div><div><div><div><div><div>Hi all,<br><br> I wanted to share a brief case study on the current dependency skew of ImgLib2-algorithm-related components.<br><br> Last week, an<span class="Apple-converted-space"> </span><a href="https://github.com/imglib/imglib2-algorithm/commit/e1460f140a0b03554fcb6f3d14ca43362d7d86a5" target="_parent">innocent-looking commit</a><span class="Apple-converted-space"> </span>was merged into imglib2-algorithm. It then made its way into a patch release of imglib2-algorithm, and<span class="Apple-converted-space"> </span><a href="https://github.com/imagej/pom-imagej/commit/d28f954494f76898d80296b168b5352238d25915" target="_parent">patch release of pom-imagej</a>. Unfortunately, even a trivial package move like this is actually a breaking API change, and both the component and pom releases should have incremented a major version to indicate this.<br><br></div> Further, pom-imagej now declares a set of components that are incompatible with each other - as components downstream of imglib2-algorithm are not updated to use the new packages. Thus if these libraries were consolidated (e.g. to upload to Fiji), there would be hit by dependency skew.<br><br></div> For those interested, there are two possible solutions:<br><br></div>1) Track down all uses of the old packages, update them, cut releases, update pom-imagej.<br></div>or<br></div>2) Add deprecated, trivial extensions of the moved classes back to the old locations, which can then be removed at a later date.<br><br></div> Naturally, #2 is much simpler and thus looking more attractive right now. :) Either way, developers should be aware of the current problems with pom-imagej 5.12.3 and 5.13.0 (the latter also points to an unreleased ij1-patcher, due to incompatibilities with ImageJ 1.49p - so certainly don't use that one).<br><br><div><div> Our versioning practices are on the wiki:<span class="Apple-converted-space"> </span><a href="http://imagej.net/Architecture#Versioning" target="_parent">http://imagej.net/Architecture#Versioning</a><span class="Apple-converted-space"> </span>but please let us know if anything is unclear or hard to find.<br><br></div><div> The burden of manually accounting for SemVer changes is hopefully one we will soon be free from. For now, it's just something we have to consider whenever we cut releases.<br><br></div><div>Best,<br></div><div>Mark</div></div></div></div></div></div></blockquote></div><br></div></body></html>