Maven plugin incorrectly report up-to-date generated PDF when xInclude is used

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Create a Maven project
2. Add a docbook document that includes another one
3. Run mvn package
4. Modify the included document
5. Run mvn package

What is the expected output? What do you see instead?
You should expect the PDF to be regenerated but instead, the plugin says: 
manual.fo is up to date.

What version of the product are you using? On what operating system?
2.0.14 on Windows 7

Please provide any additional information below.
I suspect the check to compare the date of manual.xml and manual.fo but it 
should include the included documents as well

Original issue reported on code.google.com by jeffma...@gmail.com on 11 Dec 2012 at 12:10

[GoogleCodeExporter]

Hi,

thank you for your report, I will have a look at it in december.

Regards,
Cedric,

Original comment by MimilO...@gmail.com on 12 Dec 2012 at 6:35

[GoogleCodeExporter]

Hi,

the processing of xincludes is made by the xml processor, I do not have much 
the hand on it. So what I did to avoid invalid uptodate reports is to 
regenerate the file even if nothing is modified when xincludedSupported 
properties is set.

Committed in r274

Original comment by MimilO...@gmail.com on 10 Sep 2013 at 8:08

• Changed state: Fixed

[GoogleCodeExporter]

I think that this will significantly increase the build time if 
xincludedSupported is on. I think that parsing the document for getting the 
list of included documents is not a big deal and should be done in case 
xincludedSupported is on.

Original comment by jeffma...@gmail.com on 11 Sep 2013 at 4:29

[GoogleCodeExporter]

Original comment by MimilO...@gmail.com on 19 Jan 2014 at 7:11

• Added labels: Milestone-Release2.0.15

[GoogleCodeExporter]

Original comment by MimilO...@gmail.com on 19 Jan 2014 at 7:11