<div dir="ltr">Sorry, I missed this mail until now. The issue is that <optional> maven deps were not being picked up by the maven reactor build without performing the 'mvn install' step. This issue FORGE-2003, has been resolved and is now in Forge 2.10.0.Final - I will do an update and send a PR to fix this in Windup.</div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <span dir="ltr"><<a href="mailto:ozizka@redhat.com" target="_blank">ozizka@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi (Lincoln),<br>
<br>
could you please describe the issue with forge resolver more closely?<br>
I think I was hit by that few times - the app is behaving differently<br>
when I build only one module, then run test with other, and in whole run.<br>
<br>
What's the cause and what exactly does it cause - what should I count with?<br>
<br>
On unrelated note - I changed few things, rebuilt few times, and now<br>
instead of<br>
HintsClassificationsTest.testIterationVariableResolving:162<br>
expected:<3> but was:<0><br>
I have<br>
HintsClassificationsTest.testIterationVariableResolving:162<br>
expected:<3> but was:<4><br>
Which is good - the whole run sticks with the same graph :)<br>
But a bit weirder - having more nodes than the test expects...<br>
More tomorrow.<br>
<br>
Ondra<br>
_______________________________________________<br>
windup-dev mailing list<br>
<a href="mailto:windup-dev@lists.jboss.org">windup-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/windup-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/windup-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>