9:24 p.m.
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
6:09 a.m.
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(a)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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
6:34 p.m.
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(a)redhat.com
<mailto:ozizka@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(a)lists.jboss.org <mailto:windup-dev@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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
4:29 p.m.
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(a)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(a)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(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/windup-dev
>
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
windup-dev mailing
listwindup-dev@lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
12:21 p.m.
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(a)redhat.com
<mailto:ozizka@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(a)redhat.com
> <mailto:ozizka@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(a)lists.jboss.org <mailto:windup-dev@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(a)lists.jboss.org <mailto:windup-dev@lists.jboss.org>
> https://lists.jboss.org/mailman/listinfo/windup-dev
_______________________________________________
windup-dev mailing list
windup-dev(a)lists.jboss.org <mailto:windup-dev@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(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/windup-dev
3770
days inactive
3778
days old
4 comments
2 participants
participants (2)
-
Lincoln Baxter, III -
Ondrej Zizka