On Dec 8, 2008, at 7:37 AM, Vincent Siveton wrote:
> 2008/12/8 Paul Spencer <
paulsp@...>:
>>
>> On Dec 8, 2008, at 7:17 AM, Vincent Siveton wrote:
>>
>>> 2008/12/8 Lukas Theussl <
ltheussl@...>:
>>>>
>>>> I just noticed that the fml module now takes ~5min to build
>>>> instead of a
>>>> few
>>>
>>> Same for xdoc module.
>>>
>>>> secs for all other modules. There are some svn checkouts during
>>>> testing,
>>>> are
>>>> those necessary? Does it mean you can't build doxia off-line?
>>>
>>> The tests are to perform XSD validations under our current
>>> documentation. Since we add new XSD files in this release, I think
>>> these tests are useful.
>>>
>>> About off-line build, we need to be sure that latest Maven doc is
>>> again valid (and BTW doxia needs external dependencies)
>>> Instead of svn co, we could link to relative doc path, ie from
>>> doxia-module-fml using ../../../plugins/maven-ant-plugin/src/site
>>> This approach has pros/cons like svn co.
>>>
>>> WDYT?
>>
>> Why are you not using a dependency? A "svn co" does not insure a
>> reproduceable build.
>
> Using a separate dependency or a given test folder insures that the
> documentation is valid, right.
> But how to be sure that the *latest* doc is still valid under our xsd?
> Is it a reasonable test case?
I am not sure the best way to insure the documentation is in sync.
The "snippet" macro from a test case is one tool. The test cases can
verify the XSD "matches" the doc. I say "matches" because it does not
verify the documentation is in sync with the test case.
>
>
> Vincent
>
Paul Spencer
