Hmmm. Is it the scanning you need to prevent, or will the @Veto or @Requires annotations suffice? <br><br>~Lincoln<br><br>PS. Haven&#39;t had a chance to sit down and work on your issues yet, really sorry if this is holding you up. I just haven&#39;t had a chance to breathe this week!<br>
<br><div class="gmail_quote">On Wed, Nov 16, 2011 at 11:34 PM, Richard Kennard <span dir="ltr">&lt;<a href="mailto:richard@kennardconsulting.com">richard@kennardconsulting.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi guys,<br>
<br>
I&#39;ve hit a problem related to an interaction of Arquillian, Weld and Metawidget. It could probably be fixed in any one of those, and I will endaveour to<br>
fix it in Metawidget in the future, but for now I need a workaround.<br>
<br>
Basically, I need to exclude &#39;org.jboss.forge.scaffold.faces.metawidget&#39; from the Weld scanning during Arquillian unit testing. Where should I do that? I<br>
tried modifying /forge/scaffold-faces/src/main/resources/META-INF/beans.xml but I think that&#39;s the beans.xml that gets built into the app that Forge<br>
generates, *not* the beans.xml that controls the Arquillian unit testing?<br>
<br>
Regards,<br>
<br>
Richard.<br>
_______________________________________________<br>
forge-dev mailing list<br>
<a href="mailto:forge-dev@lists.jboss.org">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"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>&quot;Keep it Simple&quot;<br>