<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Sep 29, 2014 at 2:32 PM, Stan Silvert <span dir="ltr"><<a href="mailto:ssilvert@redhat.com" target="_blank">ssilvert@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1n5" class="a3s" style="overflow:hidden">I'd like to eliminate opening the WAR and have a DeploymentProcessor<br>
look in a particular directory and add the jar at deployment time. What<br>
is the cleanest way to do that?<br></div></blockquote><div><br></div><div>Simple let user create new module that has that jar in it and than in your war <br>dependencies processor add that module to deployment as dependency<br></div><div><br> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div id=":1n5" class="a3s" style="overflow:hidden">
Bonus points if you tell me that I can treat the service provider jar as<br>
a deployment and let the user upload it via CLI. :-)</div></blockquote></div>you can add module as global dependency, but that is ugly.<br><br></div><div class="gmail_extra">But what you could do is have deployment processor that would handle exactly<br>deployments and register keycloak plugins based on that.<br></div><div class="gmail_extra"> <br></div><div class="gmail_extra"><br></div></div>