Redesign Subversion support

[Martin Krischik]

After having used the Subversion support for quite a while with large Java Models I come to the conclusion that the Version Control with Subversion in its current version is completely hopeless and should be replaced with a complete redesign.

The main problem is that the current design does not scale. It works fine with 20 packages but if your work on a Java System with a import of “rt.jar” work becomes a pain.

“Add to version control” takes approx 4 hours. That in it self would not be a problem. Just do it last thing in the evening and go hope.

But that too does not work. If there is any problem then the process stops dead and I come back to the workplace to be greeted with error message.

An Error message which only has an OK but not ABORT.

But now it is Morning, now I can't wait for the Add or Checkin to finish.

But as I said: No Abort to be seen. The only option is TASKEND /F EA. Which carries the danger that I corrupt the eap file. An eap file which is not fully added to the version control.

And I have to perform a “Resync status of all packages” — which take another 10 … 15 minutes off my working days.

So what is needed:

• The Version Control Operation should run without interruption.
• Errors should be logged to an Error log and a summary should be presented at the end of the operation.
• The must be an option for the user the gracefully abort the operation.

And Last not Least: ACommit in Subversion should be atomic. It would be much better to first export all packages and then check them with one atomic commit.
[/font]

[qwerty]

OT Don't know how you managed to get this tiny font. But I can't magnify. And thus I can't read it.

q.

[Martin Krischik]

OT Don't know how you managed to get this tiny font.

Sorry, I removed the setting.

On a side line: I only use browser which allow me to set a minimum font size because I can't stand small fonts myself. But as a result I never noticed I set the font size ridiculously small. It was certainly not my intend to make reading difficult.

[qwerty]

I guess not, but your post is the first appearing in that tiny font. And - the setting did not help. Hu! Don't want to kill you thread with that OT stuff.

q.

[Martin Krischik]

I restarted the “Add to Sourcecontrol” from scratch.

And sure I was greeted with some DAO error on adding the java.lang package. Which only had an OK button.

I am a senior software developer and I always tell the junior: “An error without indication on how to solve the error is useless. And there is no need to bother the user with error message he / she can do nothing about it. Just write it to the log file”.

And speaking of it: In the last 15 years (or so) all error dialogues for desktop apps I designed hat a history function and were able to display error messages without interrupting batch processing.

Maybe I should start a 2nd thread “Redesign Error Handling”.

[Martin Krischik]

Again I have kill EA with TASKEND /F EA because the check-in I did while beeing in a meeting stopped dead with an message and now there is not enough time to let it finish (I want to go home now and I need to take the laptop with me) — And most importantly: no ABORT button.