<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks a lot guys, I will put the stuff there for now ...<div><br></div><div>Bye bye,</div><div>Steffi</div><div><br><div><div>On Jul 10, 2012, at 12:54 , Curtis Rueden wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Hi Steffi & Dscho,</div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"> </blockquote>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">Great that you start this. I agree that the pragmatic way is to port them<br>
in a dirty way now and clean things up later. Of course this incurs some<br>technical debt, but it still gets rid of more of it.</blockquote><div><br></div><div>I agree; progressive steps toward reducing and eventually eliminating ImgLib1 are good!</div>
<div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><br></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
> I have unfortunately no idea how to create a new maven package, also the<br>> descriptions I found on the internet sound rather - well - like easy to<br>> mess up. If anyone has time, it would be awesome to create a new maven<br>
> package: imglib2-algorithms-legacy which has the same dependencies as<br>> the GPL one.<br></blockquote><div><br></div><div><div>The safest way to make a new Maven project in an existing multi-module structure such as ImgLib is to copy an existing project:</div>
<div><br></div><div>$ cd imglib2/algorithms && cp -rp gpl legacy</div><div>$ cd legacy</div><div>// delete Eclipse metadata and Maven build stuff</div><div>$ rm -rf .classpath .project .settings target</div><div>
$ vi pom.xml</div>
<div>// then read through the POM and change details that differ for the new project</div><div>// then delete source files out of src and replace with your new classes</div><div><br></div></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">I will make a branch with a simple pom and will be on Skype later. Fair<br>
ennough?</blockquote><div><br></div><div>I have done this for imglib2-algorithms-legacy and pushed to master.</div><div><br></div><div>HTH,</div><div>Curtis</div><div><br></div><div><br></div><div class="gmail_quote">On Tue, Jul 10, 2012 at 11:21 AM, Johannes Schindelin <span dir="ltr"><<a href="mailto:Johannes.Schindelin@gmx.de" target="_blank">Johannes.Schindelin@gmx.de</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Steffi,<br>
<div class="im"><br>
On Tue, 10 Jul 2012, Stephan Preibisch wrote:<br>
<br>
> I intend to port the ImgLib1 algorithms that I still need in a "dirty"<br>
> way so that we can use them under ImgLib2 but they still need to be<br>
> properly ported at some point. Otherwise it will take a too long time<br>
> until we will have the time to it correctly ... I am not too happy about<br>
> this, but otherwise we will never get rid of ImgLib1 ...<br>
<br>
</div>Great that you start this. I agree that the pragmatic way is to port them<br>
in a dirty way now and clean things up later. Of course this incurs some<br>
technical debt, but it still gets rid of more of it.<br>
<div class="im"><br>
> I have unfortunately no idea how to create a new maven package, also the<br>
> descriptions I found on the internet sound rather - well - like easy to<br>
> mess up. If anyone has time, it would be awesome to create a new maven<br>
> package: imglib2-algorithms-legacy which has the same dependencies as<br>
> the GPL one.<br>
<br>
</div>I will make a branch with a simple pom and will be on Skype later. Fair<br>
ennough?<br>
<br>
Ciao,<br>
Dscho<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Please avoid top-posting, and please make sure to reply-to-all!<br>
<br>
Mailing list web interface: <a href="http://groups.google.com/group/fiji-devel" target="_blank">http://groups.google.com/group/fiji-devel</a><br>
</div></div></blockquote></div><br><div><br class="webkit-block-placeholder"></div>
-- <br>
Please avoid top-posting, and please make sure to reply-to-all!<br>
<br>
Mailing list web interface: <a href="http://groups.google.com/group/fiji-devel">http://groups.google.com/group/fiji-devel</a><br>
</blockquote></div><br></div></body></html>