Aye the addition to the gora-core pom.xml just means that the gora-core test artifact is always generated during maven life cycle phases such as package, deploy, etc. As this is now the case, the CI nightly builds seem to be working well meaning that the tests are using the correct dependency and passing... for now.
On Thu, Dec 6, 2012 at 11:05 PM, Henry Saputra <[email protected]> wrote: > Thanks for the update Lewis. Just want to confirm that fix for GORA-193 is > to modify the pom to include the test plugin right? > > - Henry > > > On Thu, Dec 6, 2012 at 2:45 PM, Lewis John Mcgibbney < > [email protected]> wrote: > >> Hi Henry, >> >> On Mon, Dec 3, 2012 at 7:06 PM, Henry Saputra <[email protected]> >> wrote: >> > Unfortunately I am pretty much out this weekend due to cold and probably >> > for some part of this week. >> >> Hopefully you are getting better., You want to see it here in >> Scotland... pure baltic is the underestimation of 2012. >> >> > Lewis, you can continue working on this or I will take a look at this >> once >> > I get my health back. >> >> I committed GORA-193 and the tests passed on build #539 >> >> https://builds.apache.org/view/G-L/view/Gora/job/gora-trunk/539/ >> >> #540 also passed, so eventually (fingers crossed) it seems like we've >> narrowed the dependency problem down and resolved it. >> >> I've re-initiated the email notifications on the trunk build, so from >> now on we will get the outcome of the builds sent to dev@ and the >> "culprits" will also receive a notification. If these get out of hand >> again we can disable them until we get the situation sorted. >> >> I think the best thing is to monitor the builds from now on however >> hopefully things are back to normal now. >> >> All the best for now >> >> Lewis >> >> >> -- >> Lewis >> -- Lewis
