Error handling improvement for building plugins
Description
Release Notes
None
Activity
Show:
Sreevatsan Raman May 12, 2017 at 11:46 PM
The failure should happen during the build time. Perhaps we can check for the export content in the maven plugin that constructs the plugin jar/json
Terence Yim March 14, 2017 at 5:28 PM
The artifact store doesn't have a notion of plugin jar vs other jar. Any jar it received is an artifact jar, which can contains plugins and/or apps and/or other stuff. Also, even an artifact jar contains classes annotated with @Plugin doesn't necessary mean it want to expose it. What we can do is to improve the deploy artifact response to include information about the artifacts, maybe as well as warning messages.
If a plugin jar does not have export content, then the plugin deployment succeeds but the plugin doesn't show up in the UI. We should improve the experience, fail the build if there is no plugin exposed by the jar being built or fail the deployment if there is no useable plugin available during deployment