Changes between Version 80 and Version 99 of InstallNotes


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

Legend:

Unmodified
Added
Removed
Modified

  • InstallNotes

    v80 v99  
    11[[TranslatedPages]]
    2 [[TOC(inline)]]
     2[[PageOutline(2-10,Table of Content)]]
    33
    4 == Semi-Stable Version ==
    5 The latest semi-stable version is always here: [/josm-tested.jar] - we don't call it a "[wiki:Releases release]" because while it is more robust than the nightly build, it doesn't usually run through as many checks as a release would.
    6 
    7 == Nightly Builds ==
    8 You can always grab the latest nightly build from
    9 [/josm-latest.jar]. Many users actually use this for their daily work.
     4Read [wikitr:/Download#Recommendedoptions Recommended options] first.
    105
    116== Running ==
    12 A working Java Runtime Environment version 7 (32 bit package ONLY, 64 bit package don't provide the trues libraries) or newer is needed to run JOSM.
     7A working Java Runtime Environment version 11 or newer is needed to run JOSM.
    138
    149=== Microsoft Windows ===
    1510Double click on the jar file.
    1611
    17 If this does not work, you probably need to install the [https://java.com/download/index.jsp Java Runtime]
    18 
    19 In more extensive edit sessions, you may get an "out of memory" error. To avoid this, the assigned memory can be increased.[[BR]]
    20 Create a shortcut like in the following example:
    21 {{{
    22 java.exe -jar -Xmx2048M "C:\PATH-TO-JOSM\josm-latest.jar"
    23 }}}
     12If this does not work, you probably need to [wikitr:/Download#Doubleclickonafiledoesnothing install the Java Runtime Environment].
    2413
    2514To avoid the Java console windows staying open, you can use `javaw.exe` instead of `java.exe`.
    2615
    27 Be carefully if you run a 64 bit version of Windows, the Java Runtime (update every month) is installed in 64 bit.
     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.
     17Both 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).
    2818
    29 But, the JAR extension only be launch with the 32 bit version of the Java Runtime (program files (x86) folder - "bin" folder) since the v8u66.
     19But, the JAR extension will only be launched with the 32-bit version of the Java Runtime ("\Program files (x86)\bin" folder, instead of "\Program files\bin" for the 64-bit version) since the v8u66 if both versions are installed.
    3020
    31 Visit 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
    32 not installed
    33 at the same location than the 32 bit (i586) package.
     21Visit 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.
     22
     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.
     24
     25But 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).
    3426
    3527=== Linux / *BSD ===
    36 ''See also'': [wiki:HowTo/JOSM-under-Linux HowTo JOSM-under-Linux]
     28''See also'': [wikitr:/HowTo/JOSM-under-Linux HowTo JOSM-under-Linux]
    3729
    3830 **packages**::
    39  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.
    4032 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.
    4133
    … …  
    4335
    4436
    45  For SUSE and Ubuntu there are also packages on this page [[Download#openSUSE|available]].
    46  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.
    4739
    48  '''using the shell'''::
     40 **using the shell**::
    4941  Go to the directory where the josm-latest.jar is and type
    5042{{{
    … …  
    6153}}}
    6254
    63  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.
    6456 '''KDE'''::
    6557  There is a [/download/tutorials/setting_up_kde.avi tutorial] on how to setup your environment to start jar-files by clicking on them.
    6658
    6759 '''GNOME'''::
    68   Right click on the JAR file, and select __O__pen with "OpenJDK7 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.
    6961
    7062 '''XGL/Compiz'''::
    … …  
    7466export AWT_TOOLKIT=MToolkit && java -jar josm-test.jar
    7567}}}
    76   as described here: http://kubasik.net/blog/index.php/2006/06/19/java-sun-150-and-xglcompiz-on-ubuntu/
    77 
    78  '''Blank window on startup'''::
    79   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.
     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/]
    8069
    8170=== MacOS ===
    … …  
    8473 This way to start JOSM should be sufficient in most cases.
    8574 
    86 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.
    8776
    88 3. If you get "The Java JAR file could not be launched", chances are you are running Java 6 rather than Java 7.  Run from a terminal to check, as nothing appears in the system log.
     773. 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.
    8978[[Image(OSX_Error.png)]]
    9079
    91804. If you need to supply parameters (e.g. -Xmx2048M to run with more Java memory) you can use the MacOS "Terminal":
    9281
    93  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)]]
    9484
    9585* Now you have two options:
    … …  
    9989java -jar FOLDER/josm-latest.jar
    10090}}}
    101  Whereas "FOLDER" should be replaced by the name of the folder you have josm-latest.jar downloaded to. If you have downloaded it to the standard MacOS "Downloads" Folder it would look like:
     91 Whereas "FOLDER" should be replaced by the name of the folder you have josm-latest.jar downloaded to. If you have downloaded it to the standard Mac OS X "Downloads" Folder it would look like:
    10292{{{
    10393#!sh
    10494java -jar Downloads/josm-latest.jar
    10595}}}
    106  * to use additional java options just add them right after "java"
    10796
    108   If you for example have experienced the "Out of memory" warning (e.g. trying to load geo-tagged photos to JOSM) you would start JOSM like this:
    109 {{{
    110 #!sh
    111 java -Xmx512M -jar FOLDER/josm-latest.jar
    112 }}}
    113 
    114   This would allow JOSM to use up to 512 MB of RAM (memory). The java option "-Xmx512M" set's the maximum Java heap size to 512 MB. You are free to replace -Xmx512M by any number appropriate for your system (e.g. -Xmx2048M or even more).
    115 
    116   By the way. To get an overview of all Java start options you can type in:
    117 {{{
    118 #!sh
    119 java -help
    120 }}}
    121 
    122 4. If you are using the Mac OS X Package and want to alter a startup parameter permanently, then you will need to alter the Info.plist file within the /Applications/JOSM.app/Contents directory. For example, to increase the maximum Java heap size from 512MB to 2048MB, either using the terminal or XCode, in the JVMOptions key alter the entry ''-Xmx512m'' to ''-Xmx2048m''.
    123 
    124 == Getting the Source ==
    125 → [[Download#Source]]
    126 
    127 == Compiling ==
    128 → [[DevelopersGuide/Compiling]]
     97== See also ==
     98* [[wikitr:/Source code#Getthesource|Get the source]]
     99* [[wikitr:/Source code#CompilingusingAnt|Compiling using Ant]]