If you move the snippet code to anther file, you need to update the wiki
page at the same time to avoid the complain.
On 8/30/11 5:08 AM, Mathieu Lalonde wrote:
>
> Thanks for the info Hadrian.
>
> One of the reasons I was asking is because I wanted to slightly re-factor the test classes
for the jdbc component as the current layout is a little fragile. This meant moving some
tagged code snippet from a test class (JdbcRouteTest) to a newly created one: JdbcRouteTestSupport.
I suspect that would break wiki links to the snippets; is that right?
>
> If so, I may skip that re-factoring step until I get karma to update the wiki. It's
probably too small an improvement to bother.
>
> Cheers,
> Mathieu
>
> ----------------------------------------
>> Subject: Re: Question about "// Snippet" blocks in unit tests
>> From: hzbarcea@gmail.com
>> Date: Mon, 29 Aug 2011 09:06:01 -0400
>> To: dev@camel.apache.org
>>
>> Mathieu, you can ignore those. There is a confluence plugin that allows us to point
in our wiki to a snippet in the source code. That insures that the code we document in the
wiki is the actual code from the sources and stays up to date.
>>
>> Hadrian
>>
>>
>> On Aug 29, 2011, at 8:47 AM, Mathieu Lalonde wrote:
>>
>>>
>>> Hi guys,
>>>
>>> I think I got confused about those snippet blocks in the test code.
>>> Are they used to extract example code snippets at release time?
>>>
>>> eg.
>>>
>>> // START SNIPPET: register
>>> JndiRegistry reg = super.createRegistry();
>>> reg.bind("testdb", ds);
>>> return reg;
>>> // END SNIPPET: register
>>>
>>> Cheers,
>>> Mathieu
>>>
>>>
>>>
>>
>
--
Willem
----------------------------------
FuseSource
Web: http://www.fusesource.com
Blog: http://willemjiang.blogspot.com (English)
http://jnn.javaeye.com (Chinese)
Twitter: willemjiang
Weibo: willemjiang