Changes between Version 76 and Version 77 of DevelopersGuide/DevelopingPlugins

Timestamp:

2016-01-19T13:48:14+01:00 (9 years ago)

Author:

kolesar

Comment:

build may fail when path contains non-ascii characters (xjc)

DevelopersGuide/DevelopingPlugins

@@ -8 +8 @@
 == Setting up the environment ==
 
- * Check out the plugin environment into an empty directory called {{{josm}}}
+ * Check out the plugin environment into an empty directory called {{{josm}}}. Make sure path contains only ASCII characters, otherwise build may fail.
 {{{
 svn co http://svn.openstreetmap.org/applications/editors/josm
 }}}
- * create a new plugin-directory {{{josm/plugins/yourpluginname}}}. You may create a copy of the template directory [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/ 00_plugin_dir_template]. It includes a directory layout, a [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/LICENSE license file] and a template for the [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/build.xml build.xml].
+ * Create a new plugin directory {{{josm/plugins/yourpluginname}}}. You may create a copy of the template directory [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/ 00_plugin_dir_template]. It includes a directory layout, a [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/LICENSE license file] and a template for the [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/build.xml build.xml].
  * Open the ant script ({{{build.xml}}}) in your plugin directory and configure the properties in the configuration section.  The important thing of your build script is, that it places some attributes into the {{{MANIFEST.MF}}} of the jar file. See below. {{{build.xml}}} in the template directory takes care of this.
  * [osm:source:/applications/editors/josm/plugins/00_plugin_dir_template/README.template This readme] explains how your plugin is built and made available to other JOSM users.