fix for locationtech bug 140 by nprigour · Pull Request #228 · locationtech/udig-platform

@nprigour

@nprigour

@eclipsewebmaster

@nprigour

Can you explain why the pull request failed. The bug refers to locationtech bug (for udig) and has nothing to do with the eclipse issue you mention above.
The past months I had created a number of pull request for udog without any such issue.
If an ECA is really needed (until now I was informed that I need to be a commiter only in the case the changes affected more than 1000 lines of code) can you advice on how to do it.

@fgdrf

I'm wondering about the result of the ip-validation. It seems it changed, I'm going to clarify with Eclipse webmaster. In addition we raised a bug for wrong link generation for locationtech github projects https://bugs.locationtech.org/show_bug.cgi?id=75

@fgdrf

@nprigour Do you have an Eclipse account? if so, please try to login and "sign" the ECA, this may help. If you don't have an account, I'll try to find out what we need to get it approved.

@nprigour

@fgdrf I just signed the ECA. Please advise on next actions

@fgdrf

@jodygarnett Could you please have a look at? From my point of view and what the Bug states it looks like patch fixes it.

@fgdrf fgdrf added this to the uDig-2.0.0 milestone

May 19, 2017

fgdrf

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Whenever a layer haven't had a transaction, a new one is introduced. This especially happens if a target layer is hit by drag&drop operations or even edits on the Table while no edit tools were involved.

👍 to merge it

@fgdrf fgdrf mentioned this pull request

Aug 13, 2017