<div dir="ltr">Eventually furnace will enforce classloader visibility constraints based on what dependencies are and are not visible on the maven compile classpath. This is just correcting the fact that we were leaking dependencies onto the compile classpath for a long time and didn't know it. </div>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 14, 2014 at 11:34 PM, Lincoln Baxter, III <span dir="ltr"><<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Unfortunately that would be incorrect. The whole point of this is that we are moving toward a real api/impl split where API classes are visible to dependent classloaders, and impl classes are not.</div>
<div class="HOEnZb"><div class="h5"><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, May 14, 2014 at 11:23 PM, Vineet Reynolds Pereira <span dir="ltr"><<a href="mailto:vpereira@redhat.com" target="_blank">vpereira@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><br>
<br>
----- Original Message -----<br>
> From: "Lincoln Baxter, III" <<a href="mailto:lincolnbaxter@gmail.com" target="_blank">lincolnbaxter@gmail.com</a>><br>
> To: "forge-dev List" <<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a>><br>
> Sent: Thursday, May 15, 2014 5:03:35 AM<br>
> Subject: [forge-dev] Build broken due to FORGE-1823 and FORGE-1824<br>
><br>
> <a href="https://issues.jboss.org/browse/FORGE-1823" target="_blank">https://issues.jboss.org/browse/FORGE-1823</a><br>
> <a href="https://issues.jboss.org/browse/FORGE-1824" target="_blank">https://issues.jboss.org/browse/FORGE-1824</a><br>
><br>
> Fixing these issue has revealed numerous places within our codebase that we<br>
> were incorrectly depending on IMPL classes that should not have been leaked<br>
> on the maven classpath.<br>
><br>
> Now that the leak has been fixed, we have to clean up the mess :) The only<br>
> compilations I know to be remaining are in the scaffold-faces project.<br>
<br>
</div>Would it be correct to fix the compilation errors in the scaffold-faces project,<br>
by adding javaee-impl as a provided dependency to this project?<br>
<br>
Some javaee-impl and transitive dependencies are required during compilation of<br>
scaffold-faces, while at runtime, this would be provided by the javaee addon.<br>
<div><br>
><br>
> It remains to be seen how many of the tests break due to this change... we'll<br>
> see.<br>
><br>
> --<br>
> Lincoln Baxter, III<br>
> <a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>
> "Simpler is better."<br>
><br>
</div>> _______________________________________________<br>
> forge-dev mailing list<br>
> <a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org" target="_blank">forge-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/forge-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/forge-dev</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.org" target="_blank">http://ocpsoft.org</a><br>"Simpler is better."
</div>