[ImageJ-devel] [fiji-devel] Re: New imglib2-algorithms-legacy

[Stephan Preibisch]

Thanks a lot guys, I will put the stuff there for now ...

Bye bye,
Steffi

On Jul 10, 2012, at 12:54 , Curtis Rueden wrote:

> Hi Steffi & Dscho,
> 
>  
> Great that you start this. I agree that the pragmatic way is to port them
> in a dirty way now and clean things up later. Of course this incurs some
> technical debt, but it still gets rid of more of it.
> 
> I agree; progressive steps toward reducing and eventually eliminating ImgLib1 are good!
> 
> 
> > I have unfortunately no idea how to create a new maven package, also the
> > descriptions I found on the internet sound rather - well - like easy to
> > mess up. If anyone has time, it would be awesome to create a new maven
> > package: imglib2-algorithms-legacy which has the same dependencies as
> > the GPL one.
> 
> The safest way to make a new Maven project in an existing multi-module structure such as ImgLib is to copy an existing project:
> 
> $ cd imglib2/algorithms && cp -rp gpl legacy
> $ cd legacy
> // delete Eclipse metadata and Maven build stuff
> $ rm -rf .classpath .project .settings target
> $ vi pom.xml
> // then read through the POM and change details that differ for the new project
> // then delete source files out of src and replace with your new classes
> 
>  
> I will make a branch with a simple pom and will be on Skype later. Fair
> ennough?
> 
> I have done this for imglib2-algorithms-legacy and pushed to master.
> 
> HTH,
> Curtis
> 
> 
> On Tue, Jul 10, 2012 at 11:21 AM, Johannes Schindelin <Johannes.Schindelin at gmx.de> wrote:
> Hi Steffi,
> 
> On Tue, 10 Jul 2012, Stephan Preibisch wrote:
> 
> > I intend to port the ImgLib1 algorithms that I still need in a "dirty"
> > way so that we can use them under ImgLib2 but they still need to be
> > properly ported at some point. Otherwise it will take a too long time
> > until we will have the time to it correctly ... I am not too happy about
> > this, but otherwise we will never get rid of ImgLib1 ...
> 
> Great that you start this. I agree that the pragmatic way is to port them
> in a dirty way now and clean things up later. Of course this incurs some
> technical debt, but it still gets rid of more of it.
> 
> > I have unfortunately no idea how to create a new maven package, also the
> > descriptions I found on the internet sound rather - well - like easy to
> > mess up. If anyone has time, it would be awesome to create a new maven
> > package: imglib2-algorithms-legacy which has the same dependencies as
> > the GPL one.
> 
> I will make a branch with a simple pom and will be on Skype later. Fair
> ennough?
> 
> Ciao,
> Dscho
> 
> --
> Please avoid top-posting, and please make sure to reply-to-all!
> 
> Mailing list web interface: http://groups.google.com/group/fiji-devel
> 
> 
> -- 
> Please avoid top-posting, and please make sure to reply-to-all!
>  
> Mailing list web interface: http://groups.google.com/group/fiji-devel

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20120710/a871a41f/attachment.html>