[ImageJ-devel] Legacy Mode work

[Curtis Rueden]

Hi Dscho,

> After my patches, all javassisted functions assume that a legacy
> service exists. I will fix this.

Thanks, let us know when you feel the branch is ready to go.

By the way, one version of the legacy branch, which included an additional
commit by me, was already merged to master. But since you have now
force-pushed that branch, sorting out the final merge to master is going to
be a little bit tricky. But at worst we can just revert the previous merge
and then cherry pick my extra commit.

Since I am home with kids in a snowstorm, I will probably not be very
available today, but it sounds like there is a bit more to be done on the
legacy branch anyway. If you run out of time, let us know and bdezonia & I
will take it from there!

Regards,
Curtis


On Thu, Dec 20, 2012 at 3:13 AM, Johannes Schindelin <
Johannes.Schindelin at gmx.de> wrote:

> Hi,
>
> On Thu, 20 Dec 2012, Johannes Schindelin wrote:
>
> > BTW I just saw that Jenkins is not happy, it thinks that legacy tests
> > are failing. But when I ran mvn locally ("mvn clean test"), things
> > worked!
>
> A rather critical error, it turns out... After my patches, all javassisted
> functions assume that a legacy service exists. I will fix this.
>
> Ciao,
> Dscho
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://imagej.net/pipermail/imagej-devel/attachments/20121220/25191181/attachment-0001.html>