267 | | === Managing a plugin in OSM.org SVN === |
268 | | There is an SVN repository for JOSM "internal" plugins in the main OSM.org SVN repository, see [osm:source:/applications/editors/josm/plugins/ here]. Note that this repository is different from the [source: main JOSM SVN repository] which only manages the JOSM core. |
269 | | |
270 | | You can easily get write access to the JOSM plugins repository by [osmwiki:Accounts#SVN_access_.28OSM_software.29 following these steps]. If your plugin should be available for other users too and if you want to integrate it into the JOSM plugin update procedure you should submit it to the JOSM plugins repository. The following [osm:source:/applications/editors/josm/plugins/00_README readme file] might be helpful too. |
271 | | |
272 | | Managing a plugin in OSM SVN instead of own systems (which is also possible) has some advantages: |
| 267 | === Managing a plugin in plugin SVN === |
| 268 | There is an SVN repository for JOSM "internal" plugins, see [source:/osm/applications/editors/josm/plugins/ here]. Note that this repository is different from the [source: main JOSM SVN repository] which only manages the JOSM core. |
| 269 | |
| 270 | You can get write access to the JOSM plugins repository by asking in a ticket here. If your plugin should be available for other users too and if you want to integrate it into the JOSM plugin update procedure you should submit it to the JOSM plugins repository. The following [source:/osm/applications/editors/josm/plugins/00_README readme file] might be helpful too. |
| 271 | |
| 272 | Managing a plugin in plugin SVN instead of own systems (which is also possible) has some advantages: |