[overlord-issues] [JBoss JIRA] (ARTIF-645) Allow users to supply extensions through a new plugin architecture

[ https://issues.jboss.org/browse/ARTIF-645?page=com.atlassian.jira.plugin.... ] Brett Meyer updated ARTIF-645: ------------------------------ Description: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JPA entities - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) Eric's demo: https://bluejeans.com/s/82tW/ The architecture should allow plugins to be deployed as JARs within Wildfly. In addition, our built-in plugins should also be delivered that way, allowing users to opt-in (rather than always take the performance hit of needlessly using the Switchyard/Teiid/RTGov plugins). was: The illustrious [~eric.wittmann] demoed his plugin architecture within APIMan, which allows users to contribute, among other things, UI components (!!!). A similar structure could be extremely valuable for Artificer. Things a plugin could contribute: - extension contract impls (ArtifactBuilder, TypeDetector, etc.) - JPA entities - UI elements (custom metadata displays, custom actions, etc.) - endpoint bindings (again, /s-ramp/model/type) Eric's demo: https://bluejeans.com/s/82tW/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)