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
-11Lines changed: 0 additions & 11 deletions
Original file line number
Diff line number
Diff line change
@@ -48,17 +48,6 @@ and modify it according to your needs. Espacially the following properties (at t
48
48
| mapping-service.packagesToScan | Packages scanned for mapping plugins in addition to plugins located in mapping-service.pluginLocation. Typically, this property has not the be changed. | edu.kit.datamanager.mappingservice.plugins.impl |
49
49
| mapping-service.executionTimeout | The timeout in seconds a plugin process, i.e., Python of Shell, may take before it is assumed to be stale. | 30 |
50
50
51
-
## Creating Mapping Plugins
52
-
53
-
There are some sample plugins available at 'edu.kit.datamanager.mappingservice.plugins.impl'. You may add your plugins to the same package and they will be available
54
-
for your mapping-service instance (as long as you kept 'mapping-service.packagesToScan' unchanged).
55
-
56
-
Optionally, you may also develop plugins in an own repository.
57
-
However, in order to do so you'll have to build the mapping-service once and you should provide 'build/libs/mapping-service-<VERSION>-plain.jar' at
58
-
as build time dependency to have the mapping plugin interface available. After building and packaging your plugin, you can copy the resulting jar file
59
-
to 'mapping-service.pluginLocation' to make the plugin available in your mapping-service instance.
60
-
61
-
62
51
## Starting the Mapping-Service
63
52
64
53
The executable jar of the mapping-service is located at 'build/libs/mapping-service-<VERSION>.jar' You should copy it to some dedicated folder,
0 commit comments