Changeset 32070 in osm
- Timestamp:
- 2016-02-17T16:36:17+01:00 (9 years ago)
- Location:
- applications/editors/josm/plugins/mapillary
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
applications/editors/josm/plugins/mapillary/INSTALL.md
r31950 r32070 17 17 Windows users can simply replace `./gradlew` with `./gradlew.bat`. 18 18 19 If you develop using the Eclipse IDE, run the following command before opening the project in Eclipse. This will download the dependencies and tells Eclipse about where these dependencies are located on your machine: 20 ```shell 21 ./gradlew eclipse 22 ``` 23 As Eclipse plugins we recommend [eclipse-pmd](http://marketplace.eclipse.org/content/eclipse-pmd) and [Anyedit tools](http://marketplace.eclipse.org/content/anyedit-tools). 24 19 25 For just building the jar-file for the plugin, run 20 26 ```shell … … 26 32 ./gradlew build 27 33 ``` 28 (look for the re sults in the directory `build/reports`)34 (look for the reports in the directory `build/reports` and for the packaged `Mapillary.jar` in the directory `build/libs`) 29 35 30 36 And finally, you can execute the following to build the plugin from source, and run the latest JOSM with the Mapillary plugin already loaded. … … 43 49 If you don't have push-access to the SVN-server, you should now be ready to go. 44 50 45 The following paragraphs only deal with transferring commits grom theGitHub-repository to the SVN-server and the other way around.51 The following paragraphs only deal with transferring commits from the git-repository to the SVN-server and the other way around. 46 52 47 53 --- … … 84 90 --- 85 91 86 If you want to commitall of the commits that you made on the _‹foo›_-branch back to SVN, then you can skip this step.92 If you want to push (or in SVN-terms _commit_) all of the commits that you made on the _‹foo›_-branch back to SVN, then you can skip this step. 87 93 88 94 Otherwise execute the following line to preserve the other commits: -
applications/editors/josm/plugins/mapillary/build.gradle
r32063 r32070 31 31 // The JOSM-version can be specified as "latest", "tested" or the numeric version number. 32 32 // When using a numeric version number you can leave out {changing=true}. 33 compile(':josm: latest'){changing=true}33 compile(':josm:9811') 34 34 // For plugins it's irrelevant, which version is specified, always the latest version is used. 35 compile ( ':apache-commons:latest'){changing=true}36 compile ( ':apache-http:latest'){changing=true}35 compile (name: 'apache-commons'){changing=true} 36 compile (name: 'apache-http'){changing=true} 37 37 38 38 testCompile 'junit:junit:4.12'
Note:
See TracChangeset
for help on using the changeset viewer.