You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,5 @@
1
-
Commons extension (name not final)
2
-
==================================
1
+
Commons extension
2
+
=================
3
3
4
4
This is an OpenRefine extension for Wikimedia Commons.
5
5
It works with OpenRefine 3.6+.
@@ -18,12 +18,12 @@ This creates a zip file in the `target` folder, which can then be [installed in
18
18
Developing it
19
19
-------------
20
20
21
-
To avoid having to unzip the extension in the corresponding directory every time you want to test it, you can also use another set up: simply create a symbolic link from your extensions folder in OpenRefine to the local copy of this repository.
22
-
You will still need to restart OpenRefine every time you make changes.
21
+
To avoid having to unzip the extension in the corresponding directory every time you want to test it, you can also use another set up: simply create a symbolic link from your extensions folder in OpenRefine to the local copy of this repository. With this setup, you do not need to run `mvn package` when making changes to the extension, but you will still to compile it with `mvn compile` if you are making changes to Java files, and restart OpenRefine if you make changes to any files.
23
22
24
23
Releasing it
25
24
------------
26
25
26
+
- Make sure you are on the `master` branch and it is up to date (`git pull`)
27
27
- Open `pom.xml` and set the version to the desired version number, such as `<version>0.1.0</version>`
28
28
- Commit and push those changes
29
29
- Add a corresponding git tag, with `git tag -a v0.1.0 -m "Version 0.1.0"`
0 commit comments