And taking a look at the test failing, it looks like it misses imports for
asserts.

I'll cut a new RC with my latest changes.

On Sun, Jun 13, 2010 at 12:07, Antoine Toulme <[email protected]>wrote:

> OK, got the cycle under control. I filed ODE-846 as a follow up and I
> committed a few changes for Buildr's hibernate task.
>
>
>
> On Sat, Jun 12, 2010 at 12:11, Antoine Toulme <[email protected]>wrote:
>
>> Commenting on my own email:
>>
>> On Sat, Jun 12, 2010 at 01:01, Antoine Toulme <[email protected]>wrote:
>>
>>> I tried some functional testing of RC4 with Apache ODE.
>>>
>>> It didn't play well.
>>>
>>> First, here is still an issue with tag_name over git. I thought this was
>>> fixed, but our API obviously is still not ready. We should at the very least
>>> die with a deprecation message. I'll work on that this week-end.
>>>
>> Fixed now.
>>
>>>
>>> Second, with jruby, I got this annoying stacktrace:
>>> http://jira.codehaus.org/browse/JRUBY-4867
>>> Turns out our buildr script for jruby needed to be updated for version
>>> 1.5.1. Fixed now.
>>>
>>> Third, I ran into issues with cycle detection.
>>> Commenting out the Rake monkey-patching in application.rb fixes the issue
>>> - I need to hack it some more.
>>>
>> Looks like BUILDR-399 causes the problem. Looks also like BUILDR-354 is
>> unrelated.
>> I'm wondering if the Rakefile of ODE is the problem - after all, it was
>> one of the first Rakefile and may contain some stale stuff.
>>
>>>
>>> Fourth, compilation fails because jmock and junit are not found.
>>>
>> Not there yet.
>>
>>>
>>> I'm not happy with this mess. I intend to start having rounds of
>>> functional testing harnessed in Hudson.
>>>
>> Ongoing - I detailed my plan in BUILDR-456.
>>
>>>
>>> I'll probably sacrifice part of my week-end over this.
>>>
>>> Thanks,
>>>
>>> Antoine
>>>
>>>
>>>
>>
>

Reply via email to