<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 8, 2015 at 5:02 PM, Sanne Grinovero <span dir="ltr"><<a href="mailto:sanne@hibernate.org" target="_blank">sanne@hibernate.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div id=":29q" class="" style="overflow:hidden">Personally, I would totally love such an appserver who's going to yell at me:<br>
"you bundled two copies of blah, I refuse to deploy that!".<br>
<br>
Or similarly: "you're bundling Hibernate, but we're giving it to you<br>
already as we recognized a JPA app and you didn't disable the embedded<br>
module!"<br>
<br>
"Seriously, one more copy of the JTA API ?"</div></blockquote></div><br><br></div><div class="gmail_extra">I've actually done some initial work on this, but never managed to get code to some "stable" phase<br></div><div class="gmail_extra">where it could be used for some more than just demo purposes. (it was presented at London JBUG last year)<br><br></div><div class="gmail_extra">But idea was to do just that, have configurable set of "problematic" bundled jars / classes<br></div><div class="gmail_extra">that server would than yell at you about.<br><br></div><div class="gmail_extra">hence the name silly deployment detector.<br></div><div class="gmail_extra">code of it could be found <a href="https://github.com/ctomc/wildfly-sdd">https://github.com/ctomc/wildfly-sdd</a><br><br></div><div class="gmail_extra">With some more effort it could be brought to usable tool to help with messed up deployments.<br><br>--<br></div><div class="gmail_extra">tomaz<br></div></div>