Changes between Version 92 and Version 99 of InstallNotes


Ignore:
Timestamp:
(multiple changes)
Author:
(multiple changes)
Comment:
(multiple changes)

Legend:

Unmodified
Added
Removed
Modified

  • InstallNotes

    v92 v99  
    22[[PageOutline(2-10,Table of Content)]]
    33
    4 Read [[Download#Recommendedoptions]] first.
     4Read [wikitr:/Download#Recommendedoptions Recommended options] first.
    55
    66== Running ==
    7 A working Java Runtime Environment version 8 or newer is needed to run JOSM.
     7A working Java Runtime Environment version 11 or newer is needed to run JOSM.
    88
    99=== Microsoft Windows ===
    1010Double click on the jar file.
    1111
    12 If this does not work, you probably need to [wiki:Download#Doubleclickonafiledoesnothing install the Java Runtime Environment].
     12If this does not work, you probably need to [wikitr:/Download#Doubleclickonafiledoesnothing install the Java Runtime Environment].
    1313
    1414To avoid the Java console windows staying open, you can use `javaw.exe` instead of `java.exe`.
    1515
    16 Be carefully if you run a 64-bit version of Windows, the Java Runtime (update every month) may be installed in 64-bit when visiting the Java web site with a 64-bit version of your browser, or in 32-bit otherwise.
     16Be careful if you run a 64-bit version of Windows, the Java Runtime (update every month) may be installed in 64-bit when visiting the Java website with a 64-bit version of your browser, or in 32-bit otherwise.
    1717Both Java platforms will coexist on the PC, but by default the file associations will run first the 32-bit version, creating VMs limited to a maximum of 247MB (if your VM size reaches this limit, due to the volume of data loaded, JOSM may become very slow or unresponsive).
    1818
    … …  
    2121Visit the www.java.com main site, choose to download java ... and chose the i586 package. You can keep the 64-bit package because it is not installed at the same location than the 32-bit (i586) package.
    2222
    23 If only a 64-bit version of Java is installed on a 64-bit version of Windows (and with a Java version higher or equal to the minimum version specified in the JNLP if you use JavaWebStart to download/update and launch JOSM), JOSM will start automatically in a 64-bit Java VM (with more memory available to handle larger volumes of data, and better performance). Otherwise it will launch in a 32-bit Java VM, unless you add VM parameters to the command line to locate and use the 64-bit version of Java.
     23If only a 64-bit version of Java is installed on a 64-bit version of Windows (and with a Java version higher or equal to the minimum version specified in the JNLP if you use JavaWebStart to download/update and launch JOSM), JOSM will start automatically in a 64-bit Java VM (with more memory available to handle larger volumes of data, and better performance). Otherwise, it will launch in a 32-bit Java VM, unless you add VM parameters to the command line to locate and use the 64-bit version of Java.
    2424
    2525But you may also uninstall any 32-bit versions of Java if you don't need applets in a 32-bit browser (the 32-bit version of Java remains useful when using an old 32-bit browser for using applets in web pages, or for 32-bit OSes where this is the only choice available on the web or in standalone usage).
    2626
    2727=== Linux / *BSD ===
    28 ''See also'': [wiki:HowTo/JOSM-under-Linux HowTo JOSM-under-Linux]
     28''See also'': [wikitr:/HowTo/JOSM-under-Linux HowTo JOSM-under-Linux]
    2929
    3030 **packages**::
    31  In some Distributions prepacked packages exist to install JOSM with your favorite package manager from the repositories.
     31 In some Distributions, prepacked packages exist to install JOSM with your favorite package manager from the repositories.
    3232 Although these packages might be a bit older than the .jar files on the main page, they usually fit better into the environment and install dependencies and a starter in the menu automatically.
    3333
    … …  
    3535
    3636
    37  For SUSE and Ubuntu there are also packages on this page [[Download#openSUSE|available]].
    38  If there exists no package or you do not want to use it you can download the JOSM .jar file from the [WikiStart main page] (tested or latest version) or build it from source.
     37 For SUSE and Ubuntu/Debian, there are also packages on this page available ( [wikitr:/Download#openSUSE SUSE], [wikitr:/Download#Ubuntu Ubuntu]).
     38 If there exists no package or you do not want to use it you can download the JOSM .jar file from the [wikitr:/WikiStart main page] (tested or latest version) or build it from source.
    3939
    40  '''using the shell'''::
     40 **using the shell**::
    4141  Go to the directory where the josm-latest.jar is and type
    4242{{{
    … …  
    5353}}}
    5454
    55  See also [wiki:Help/CommandLineOptions command line options] and [wiki:HowTo/JOSM-under-Linux Josm under Linux Howto] for additional info.
     55 See also [wikitr:/Help/CommandLineOptions command line options] and [wikitr:/HowTo/JOSM-under-Linux Josm under Linux Howto] for additional info.
    5656 '''KDE'''::
    5757  There is a [/download/tutorials/setting_up_kde.avi tutorial] on how to setup your environment to start jar-files by clicking on them.
    5858
    5959 '''GNOME'''::
    60   Right click on the JAR file, and select __O__pen with "OpenJDK8 Runtime", or whatever Java version you have.
     60  Right-click on the JAR file, and select __O__pen with "OpenJDK11 Runtime", or whatever Java version you have.
    6161
    6262 '''XGL/Compiz'''::
    … …  
    6666export AWT_TOOLKIT=MToolkit && java -jar josm-test.jar
    6767}}}
    68   as described here: http://kubasik.net/blog/index.php/2006/06/19/java-sun-150-and-xglcompiz-on-ubuntu/
     68  as described here: [https://web.archive.org/web/20060718112352/http://kubasik.net/blog/index.php/2006/06/19/java-sun-150-and-xglcompiz-on-ubuntu/ http://kubasik.net/blog/index.php/2006/06/19/java-sun-150-and-xglcompiz-on-ubuntu/]
    6969
    70  '''Blank window on startup'''::
    71   AWT before JDK7 [http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6574362 doesn't play well] with non-reparenting window managers (i.e. xmonad, awesome, dwm, ratpoison, Ion3, ...), resulting in the main window not being displayed properly on startup.  The Awesome Wiki has [http://awesome.naquadah.org/wiki/Problems_with_Java workarounds] for this problem.  There is also an [http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Hooks-SetWMName.html xmonad specific] way of doing the wmname thing.
    72 
    73 === Mac OS X ===
    74 1. If you have downloaded `josm-latest.jar` you can start JOSM by clicking on the josm-latest.jar file in the Mac OS X Finder (you might get the warning that you are about to open a file from the internet - just accept).
     70=== MacOS ===
     711. If you have downloaded `josm-latest.jar` you can start JOSM by clicking on the josm-latest.jar file in the MacOS Finder (you might get the warning that you are about to open a file from the internet - just accept).
    7572
    7673 This way to start JOSM should be sufficient in most cases.
    7774 
    78 2. If you are running Mountain Lion, you will need to temporarily disable Gatekeeper. Otherwise, you will be unable to open josm and upon launching josm, receive the error message "JOSM.app is damaged and can't be opened. You should move it to the Trash." Disable Gatekeeper by opening System Preferences > Security & Privacy, and setting 'Allow applications downloaded from:' to 'Anywhere'. Once you open the application, you can re-enable gatekeeper, and it appears that JOSM will open again without a problem. See [osmwww:user/drnoble/diary/17636 this] and #7904 for more information.
     752. If you are running Mountain Lion, you will need to temporarily disable Gatekeeper. Otherwise, you will be unable to open josm and upon launching josm, receive the error message "JOSM.app is damaged and can't be opened. You should move it to the Trash". Disable Gatekeeper by opening System Preferences > Security & Privacy, and setting 'Allow applications downloaded from:' to 'Anywhere'. Once you open the application, you can re-enable gatekeeper, and it appears that JOSM will open again without a problem. See [osmwww:user/drnoble/diary/17636 this] and #7904 for more information.
    7976
    80773. If you get "The Java JAR file could not be launched", chances are you are running an old Java version.  Run from a terminal to check, as nothing appears in the system log.
    8178[[Image(OSX_Error.png)]]
    8279
    83 4. If you need to supply parameters (e.g. -Xmx2048M to run with more Java memory) you can use the Mac OS X "Terminal":
     804. If you need to supply parameters (e.g. -Xmx2048M to run with more Java memory) you can use the MacOS "Terminal":
    8481
    85  Start the "Terminal" application (e.g. by typing "Terminal" into the Spotlight search)
     82 Start the "Terminal" application (e.g. by typing "Terminal" into the Spotlight Search, ⌘+space)
     83[[Image(SearchTerminal.png)]]
    8684
    8785* Now you have two options:
    … …  
    9896
    9997== See also ==
    100 * [[Source code#Getthesource]]
    101 * [[Source code#CompilingusingAnt]]
     98* [[wikitr:/Source code#Getthesource|Get the source]]
     99* [[wikitr:/Source code#CompilingusingAnt|Compiling using Ant]]