KPM 으로 플러그인 설치법
https://github.com/killbill/killbill-cloud/blob/master/kpm/README.md#dev-mode
Dev Mode
If you are a developer and either modifying an existing plugin or creating a new plugin, KPM can be used to install the code of your plugin. Before we look at KPM commands, make sure you read the Plugin Development Documentation.
Let 's assume we are modifying the code for the (ruby) cybersource plugin. You would have to first build the plugin package, and then you could use KPM to install the plugin. We suggest you specify a plugin_key with a namespace dev: to make it clear this is not a released version. Also in the case of ruby, the package already contains all the directory structure including the version, so only the location of the tar.gz needs to be specified.
> kpm install_ruby_plugin 'dev:cybersource' --from-source-file="<PATH_TO>/killbill-cybersource-3.3.0.tar.gz"
Let 's assume now that we are modifying the code for the (java) adyen plugin. The plugin first needs to be built using the maven-bundle-plugin to produce the OSGI jar under the target directory. Then, this jar can be installed but here we also need to specify a version since the archive does not embed any filesystem structure but only contains the binary (jar). The same applies with regard to the plugin_key where we suggest to specify a namespace dev:.
> kpm install_java_plugin 'dev:adyen' --from-source-file="<PATH_TO>/adyen-plugin-0.3.2-SNAPSHOT.jar" --version="0.3.2"
The command kpm inspect can be used to see what has been installed. In the case of dev plugin most info related to GROUP ID, ARTIFACT ID, PACKAGING and SHA1 will be missing because no real download occured.
Finally, when it is time to use a released version of a plugin, we first recommend to uninstall the dev version, by using the kpm uninstall command and using the plugin_key and then installing the released version. For instance the following sequence could happen:
> kpm inspect
___________________________________________________________________________________________________________________________
| PLUGIN NAME | PLUGIN KEY | TYPE | GROUP ID | ARTIFACT ID | PACKAGING | VERSIONS sha1=[], def=(*), del=(x) |
___________________________________________________________________________________________________________________________
| killbill-cybersource | dev:cybersource | ruby | ??? | ??? | ??? | 3.3.0[???](*) |
| adyen | dev:adyen | java | ??? | ??? | ??? | 0.3.2[???](*) |
___________________________________________________________________________________________________________________________
> kpm uninstall 'dev:cybersource'
Removing the following versions of the killbill-cybersource plugin: 3.3.0
Done!
> kpm inspect
_____________________________________________________________________________________________________________
| PLUGIN NAME | PLUGIN KEY | TYPE | GROUP ID | ARTIFACT ID | PACKAGING | VERSIONS sha1=[], def=(*), del=(x) |
_____________________________________________________________________________________________________________
| adyen | dev:adyen | java | ??? | ??? | ??? | 0.3.2[???](*) |
_____________________________________________________________________________________________________________
> kpm install_ruby_plugin cybersource
[...]
> kpm inspect
_______________________________________________________________________________________________________________________________________________________
| PLUGIN NAME | PLUGIN KEY | TYPE | GROUP ID | ARTIFACT ID | PACKAGING | VERSIONS sha1=[], def=(*), del=(x) |
_______________________________________________________________________________________________________________________________________________________
| killbill-cybersource | cybersource | ruby | org.kill-bill.billing.plugin.ruby | cybersource-plugin | tar.gz | 4.0.2[e0901f..](*) |
| adyen | dev:adyen | java | ??? | ??? | ??? | 0.3.2[???](*) |
_______________________________________________________________________________________________________________________________________________________
KPM 으로 플러그인 설치법
https://github.com/killbill/killbill-cloud/blob/master/kpm/README.md#dev-mode
Dev Mode
If you are a developer and either modifying an existing plugin or creating a new plugin, KPM can be used to install the code of your plugin. Before we look at KPM commands, make sure you read the Plugin Development Documentation.
Let 's assume we are modifying the code for the (ruby) cybersource plugin. You would have to first build the plugin package, and then you could use KPM to install the plugin. We suggest you specify a
plugin_keywith a namespacedev:to make it clear this is not a released version. Also in the case ofruby, the package already contains all the directory structure including the version, so only the location of thetar.gzneeds to be specified.Let 's assume now that we are modifying the code for the (java) adyen plugin. The plugin first needs to be built using the
maven-bundle-pluginto produce the OSGI jar under thetargetdirectory. Then, thisjarcan be installed but here we also need to specify a version since the archive does not embed any filesystem structure but only contains the binary (jar). The same applies with regard to theplugin_keywhere we suggest to specify a namespacedev:.The command
kpm inspectcan be used to see what has been installed. In the case ofdevplugin most info related toGROUP ID,ARTIFACT ID,PACKAGINGandSHA1will be missing because no real download occured.Finally, when it is time to use a released version of a plugin, we first recommend to uninstall the
devversion, by using thekpm uninstallcommand and using theplugin_keyand then installing the released version. For instance the following sequence could happen: