Recognize svn errors

[Iritscen]

Although I'm not sure how this happened, I think I may have manually replaced the AEI with a different build at some point. This caused the following error, according to 'svn st':

A  +  C *        -   AEInstaller2.jar
      >   local edit, incoming replace upon update
        *       96   .
Status against revision:     96
Summary of conflicts:
  Tree conflicts: 1

When launching the AEI, this unseen conflict caused the update check to silently fail. There was no way to know there was a newer version available.

I don't know what is the best way to solve this, but it seems that the 'C' on the first line of output is the key indicator that there's a conflict, so if we look for that, at least we can warn the user that there is an issue, and perhaps prompt him to delete bin/ and run the updater (on the Mac, opening "Run the AE Installer" will run the updater when the AEI is not present).

P.S.: 'svn help st' shows all possible return values for the seven columns of output (the above 'C' is in the 7th column). Though handling all those possible codes would be a lot of work, perhaps if we are just putting up a generic dialog about deleting bin/, then the AEI only needs to watch for any return code that is not normal (normal being 'M', etc.).

[Christian]

No real change here but at least the updater's log should now (updater 1.3) give more information (well, in most cases "any information at all" unlike before ;) ) on what's happening during the updater runs.