Appian 17.1 Plugin common libraries

RE: Appian 17.1 Plugin common libraries

Eliot Gerson — Thu, 09 Feb 2017 00:23:08 GMT

@thanosm, as stated in the documentation, "only use Appian's public Java API to invoke Appian functionality" in plugins. You can find the public API here: docs.appian.com/.../ . As long as you adhere to the guidelines in the documentation, you should be fine.

RE: Appian 17.1 Plugin common libraries

thanosm — Wed, 08 Feb 2017 15:18:24 GMT

Thanks for that info! I take it that Appian still does not allow the use of Jars from its Appian.ear\\lib folder by custom plugins.

RE: Appian 17.1 Plugin common libraries

Jim Schweitzer — Wed, 08 Feb 2017 13:42:59 GMT

I just have a separate common location where I keep the appian jars on the dev machine (could be an appian install folder, or just a copy). They just use "Add External Jars" to point to that common location in configure build path in eclipse.

RE: Appian 17.1 Plugin common libraries

thanosm — Wed, 08 Feb 2017 13:26:49 GMT

How would you go about doing that? In previous versions i have not been able to accomplish that.

RE: Appian 17.1 Plugin common libraries

Jim Schweitzer — Wed, 08 Feb 2017 12:20:10 GMT

I would just add externalize the reference to the appian jars in the classpath, then you don't have to bundle it with the plugin jar. It'll just use the libs that are present on the target system