[windup-dev] Double building?

Ondrej Zizka ozizka at redhat.com
Thu Sep 18 13:21:33 EDT 2014


I will get back to it when it occurs again, which is typically when 
figuring out why something doesn't work, which I believe will be soon :)


On 17.9.2014 23:29, Lincoln Baxter, III wrote:
> Please explain this behavior in more detail. Steps to reproduce. I 
> will try to debug, but a bit busy at the moment to work on a 
> non-critical issue :) so it might wait.
>
> On Sun, Sep 14, 2014 at 7:34 PM, Ondrej Zizka <ozizka at redhat.com 
> <mailto:ozizka at redhat.com>> wrote:
>
>     If it's fixed, then just out of curiosity - mvn install of what?
>     When I did `mvn install` over the whole project, e.g. graph should
>     be already `mvn install`ed before it gets to windup-tests module.
>     So I wonder why I was seeing behavior which I'd classify as forge
>     not picking up the freshly built artifact.
>
>     Thanks,
>     Ondra
>
>
>
>     On 12.9.2014 13:09, Lincoln Baxter, III wrote:
>>     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.
>>
>>     On Tue, Sep 9, 2014 at 10:24 PM, Ondrej Zizka <ozizka at redhat.com
>>     <mailto:ozizka at redhat.com>> wrote:
>>
>>         Hi (Lincoln),
>>
>>         could you please describe the issue with forge resolver more
>>         closely?
>>         I think I was hit by that few times - the app is behaving
>>         differently
>>         when I build only one module, then run test with other, and
>>         in whole run.
>>
>>         What's the cause and what exactly does it cause - what should
>>         I count with?
>>
>>         On unrelated note - I changed few things, rebuilt few times,
>>         and now
>>         instead of
>>          HintsClassificationsTest.testIterationVariableResolving:162
>>         expected:<3> but was:<0>
>>         I have
>>          HintsClassificationsTest.testIterationVariableResolving:162
>>         expected:<3> but was:<4>
>>         Which is good - the whole run sticks with the same graph :)
>>         But a bit weirder - having more nodes than the test expects...
>>         More tomorrow.
>>
>>         Ondra
>>         _______________________________________________
>>         windup-dev mailing list
>>         windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>>         https://lists.jboss.org/mailman/listinfo/windup-dev
>>
>>
>>
>>
>>     -- 
>>     Lincoln Baxter, III
>>     http://ocpsoft.org
>>     "Simpler is better."
>>
>>
>>     _______________________________________________
>>     windup-dev mailing list
>>     windup-dev at lists.jboss.org  <mailto:windup-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>     _______________________________________________
>     windup-dev mailing list
>     windup-dev at lists.jboss.org <mailto:windup-dev at lists.jboss.org>
>     https://lists.jboss.org/mailman/listinfo/windup-dev
>
>
>
>
> -- 
> Lincoln Baxter, III
> http://ocpsoft.org
> "Simpler is better."
>
>
> _______________________________________________
> windup-dev mailing list
> windup-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/windup-dev/attachments/20140918/2424c261/attachment.html 


More information about the windup-dev mailing list