Alexei Barantsev wrote:
>Actually, it is not enough to copy HTML files.
>
>Sometimes there are other kinds of files to copy (for example, I have
>XML Shema files).
>Sometimes there are XML files that are not xdoc and should not be
>transformed but just copyed (I have examples that are XML files in my
>project documentation).
>
>I'd suggest:
>either
> - take directory out of ./xdocs/, for example ./docs/, and copy its
>content to ./target/docs/ as is;
>or
> - take subdirectory, for example, ./xdocs/resources/, and copy it to
>./target/docs/resources/ with all its content as is, and exclude it from
>DVSL processing.
>
>Best regards,
>
>
Hi,
What about a layout guided by the plugins ?
By this I mean that a plugin would take its sources from
src/${plugin.name} and process what it has to process to
target/${plugin.name}.
This would give something like src/xdoc, which would be
output to target/xdoc. Then, it would be easier for the
end user to know what is used to do what, and where it
goes to. We already have src/java and src/test.
The plugin base for Maven is starting to get really huge,
and it will for sure get bigger. This way, one could know
what plugins are used simply looking at the dir structure.
I know that this would need quite some important refactorings,
but IMO the learning curve would be much smaller.
We could even implement some properties, like
plugin.src.dir -> ${maven.src.dir}/${plugin.name}
plugin.target.dir -> ${maven.build.dir}/${plugin.name}
that would be made available to the plugin (like ${plugin.dir})
, so that we don't have to bother where the files are taken
and where we may output something.
Any thoughts ?
Thanks,
St�phane
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
