I did some investigating and found out the problem. Between version 1.1.0 and version 1.3.0, the way libraries shipped changed. They lost the version number. However the new names is only included in the full versions (like version 1.3.0), and not in the fix version (1.3.1).

This means that if you download vcc-max-1.1.0.dmg, upgrade to 1.3.0 first, then to 1.3.1, it should work.

I really need to refresh the MAC DMG to a newer version.

Could you test this upgrade route? If this works, maybe VCC should enforce this logic in the upgrade path.

As I understand Help -> Check for Updates will not work anyway ?

It should work. If you go from 1.1.0 to 1.3.0, then 1.3.1. Use the Help -> Check fro Updates, select version 1.3.0. Once this update is done, you can update to 1.3.1.

I'll try to add this logic in the update mechanism, so that it does not happen again.

Yes, I can confirm, it works that way:
Install 1.1 dmg,
Run Help -> Check for Updates, select and install 1.3.0 version
Run Help -> Check for Updates, select and install 1.3.1 version

It works

but Java/lib/ has all libraries twice, and with different sizes:

$ ls -al /Applications/DnD/Virtual\ Combat\ Cards.app/Contents/Resources/Java/lib/
total 24184
drwxr-xr-x 25 vova admin 850 Aug 27 13:10 .
drwxr-xr-x 13 vova admin 442 Aug 27 13:10 ..
-rw-r--r-- 1 vova admin 1079323 Aug 27 13:10 core-renderer.jar
-rw-r--r-- 1 vova admin 734672 Aug 27 13:10 idw-gpl.jar
-rw-r--r-- 1 vova admin 516429 Nov 30 2009 jetty-6.1.14.jar
-rw-r--r-- 1 vova admin 163122 Nov 30 2009 jetty-util-6.1.14.jar
-rw-r--r-- 1 vova admin 177182 Aug 27 13:10 jetty-util.jar
-rw-r--r-- 1 vova admin 538064 Aug 27 13:10 jetty.jar
-rw-r--r-- 1 vova admin 240 Aug 27 13:10 library.lst
-rw-r--r-- 1 vova admin 391834 Nov 30 2009 log4j-1.2.15.jar
-rw-r--r-- 1 vova admin 391834 Aug 27 13:10 log4j.jar
-rw-r--r-- 1 vova admin 74535 Nov 30 2009 miglayout-3.6.2-swing.jar
-rw-r--r-- 1 vova admin 194875 Aug 27 13:10 miglayout.jar
-rw-r--r-- 1 vova admin 9135 Nov 30 2009 sample-comp.zip
-rw-r--r-- 1 vova admin 3789991 Aug 27 13:10 scala-library.jar
-rw-r--r-- 1 vova admin 623359 Aug 27 13:10 scala-swing.jar
-rw-r--r-- 1 vova admin 132367 Nov 30 2009 servlet-api-2.5-6.1.14.jar
-rw-r--r-- 1 vova admin 134133 Aug 27 13:10 servlet-api.jar
-rw-r--r-- 1 vova admin 23445 Nov 30 2009 slf4j-api-1.5.8.jar
-rw-r--r-- 1 vova admin 23671 Aug 27 13:10 slf4j-api.jar
-rw-r--r-- 1 vova admin 9679 Nov 30 2009 slf4j-log4j12-1.5.8.jar
-rw-r--r-- 1 vova admin 9693 Aug 27 13:10 slf4j-log4j12.jar
-rw-r--r-- 1 vova admin 1539586 Aug 27 13:10 vcc-dnd4e.jar
-rw-r--r-- 1 vova admin 6371 Aug 27 13:10 vcc-run.jar
-rw-r--r-- 1 vova admin 1766801 Nov 30 2009 vcc.jar
$

Another strange thing is that
Help -> About (unusual thing for MacOS applications) shows 1.3.1 version, but
Virtual Combat Cards -> About (usual place for MacOS applications) shows 1.1 version

see shots

Regarding comment #5 that is a known issue. The issue is that the information from the Mac panel comes from a file that does not get updated.

I moved this problem to it's own issue: #188: Mac OS shows incorrect version of VCC. Since this is more general, I'm changing the title (the problem will happen with anyone upgrading from a while back). It surfaced on the Mac because the DMG is really old.

Implemented logic to filter out versions which will not update corretly. Update may require two steps, but the new logic will ensure all dependencies are corretly resolved, and tha upgrades are applied in the correct order.

To complete this fix a new Mac OS DMG will be created, and the old one removed. Maybe we should relocate the old version.

Fixed on version 1.4.0.

Automatically closed -- issue fixed for two weeks with no activity.