Menu

#2214 Adding updateUrl to add-on leads to installation error

Next Release
fixed
nobody
None
normal
minor
Always
none
Windows 7
jre1.8.0_40
2016-03-18
2015-03-28
No

In a add-on mind map you can enter an update URL. It is not clear whether one should include the file name 'version.properties' in the URL or not, but this bug can be reproduced for both variants.

Example of update URL entered in add-on mind map.

If you enter a updateUrl and then install the add-on, this will lead to the following error:
"Cannot cast object '<entered update="" url="">' with class 'java.net.URI' to class 'java.net.URL'"</entered>

Error message with regard to update URL

If you add the same link as a link to the root node of the add-on and leave updateUrl empty, this error will not occur.

2 Attachments

Related

Old Bug Tickets replaced by GitHub Issues: #2214

Discussion

  • zipizap

    zipizap - 2016-03-16

    This bug is still present in Freeplane 1.5.7 beta (march 2016)

    If you create an addon, with the attribute "updateUrl" empty, the addon will install correctly with no error.
    However if you build the addon with the attribute "updateUrl" filled with text specifiyng a url to the version.properties file (ex: updateUrl = https://raw.githubusercontent.com/zipizap/FreeplaneJrubyInstaller/early_stage/addon_lab/version.properties), then when installing the addon the error will show up and the addon will not be installed.

    This bug cripples the update-mechanism for addons: it impedes the definition of the url pointing to the file "version.properties" which is the recommended way to check if there is an updated-version of the addon that should be downloaded.

    To help debug this, I leave attached an image showing the error, and the log containing theinstallation error.

    I cross my fingers that this gets fixed at some point - I'm planning on releasing an addon, and it would be great to use this existing update-mechanism to maintain it up-to-date as newer versions get released.

     

    Last edit: zipizap 2016-03-16
  • Volker Börchers

    • status: new --> fixed
     
  • Volker Börchers

    Thanks for reporting this issue that arose from hyperlink recognition in attribute values.
    Will be fixed in next 1.5.x release