Maven 1.x FAQ Plugin

This would be nice. Got a patch?

>This would be nice. Got a patch?

well, ... no i didn't, ... but know I do
figured I could give it a go and might learn some jelly on the way.

So I've made a patch, which extends faq to handle multiple input files. Generally, it works by using two properties:

<---

1. Where source *.fml files are looked for
   maven.faq.src=${basedir}/xdocs

1. Destination directory where output xdocs file are produced
   maven.faq.dest=${maven.build.dir}/generated-xdocs
   <---

It will also map the directory structure from source into target.

I will be attaching the patch, and hope someone will apply it.

BTW: I've not changed the docs for it yet. Want to see if someone thinks it is good enough for commit - then I'll be happy to update the docs !!

okay?

Here's the patch for multiple faq .fml files processing in the faq-plugin.
It includes a "cvs diff -u" for the changed plugin.jelly file and a collection of the few new files.

The patch is made against HEAD 20031009.

I don't think you need the FileHelper class.

Check how the xdoc plugin does it using a 'mapper'.

Okay thanks! Actually I fiddled a lot with it, to and do it all in jelly. I'll give it a try some time tonight I think

Okay, I've had a look at how the xdoc plugin does it. Of course, you were right. I could very well do without the FileHelper class.

So, I removed FileHelper, and did it all in Jelly using the CaseInsensitiveGlobPatternMapper.

I'm going to attach a new patch i a minute!

Thanx!

A patch for faq to handle multiple .fml file transformations, which does not use the FileHelper class.
Actually also fixes a TODO in the faq-plugin, about making it a defined tag.

Patch applied with small change.
Test project added.
Fixed in 1.2-SNAPSHOT

I think this deserves a release of the FAQ plugin.

Thoughts?

Would be nice with a release yes.

One thought though. I came to think about backward compatibility. Anyone having used the previous src and dest file properties - eg. to name the dest not like src - will have a broken build (broken links) in their docs.

Maybe we should issue a warning, if the old props are set?