Yes, that looks like a bug alright. And it needs a unit test too,
obviously!
Will fix this ASAP.
On Wed, Jul 3, 2013 at 4:43 PM, Maciej M. Latek <[email protected]> wrote:
> Hi,
>
> I have noticed that AbstractSTRtree might be having a problem with its
> remove() method:
>
> protected boolean remove(Object searchBounds, Object item) {
> build();
> if (itemBoundables.isEmpty()) {
> Assert.isTrue(root.getBounds() == null);
> }
> ...
>
> I believe that build() always sets itemBoundables to null. I believe
> problem started when I upgraded to 1.13 from version 1.8.
>
> Best regards,
>
> Maciej
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> Jts-topo-suite-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/jts-topo-suite-user
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Jts-topo-suite-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jts-topo-suite-user
