<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Wed, Jun 4, 2014 at 7:31 PM, James R. Perkins <span dir="ltr"><<a href="mailto:jperkins@redhat.com" target="_blank">jperkins@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Currently the EAR/META-INF directory is not visible to it's sub-modules.<br>
Should we expose the EAR/META-INF directory to the class path?<br>
<br>
I've seen questions a few times when a user wants to use their own copy<br>
of log4j in an EAR and they place the log4j.xxx configuration file in<br>
the EAR/META-INF directory. Since the log4j.jar doesn't have the<br>
directory on it's class path the conflagration file can not be read.<br>
<br>
Anyone have thoughts or opinions on this?</blockquote><div><br></div><div>I think the EAR's root is a very logical place to put configuration files like that. There really is no good other location. Picking a random EJB module and putting it there is weird, and putting it in every individual WEB module is weird too.</div>
<div><br></div><div>If anything, especially with the upcoming configuration JSR in mind, I think the Java EE spec should just demand that EAR/META-INF is on the class path.</div><div><br></div><div>So I'd love JBoss/WildFly to have this as a proprietary option, but eventually it should be handled by the spec too.</div>
<div><br></div><div>Kind regards,</div><div>Arjan</div><div><br></div><div> </div></div></div></div>