Eric Weidner wrote:
> Is there an easy way to use only the project documentation
> capabilities of Maven in b5? I've tried doing 'maven site' and this
> comes pretty close to doing what I want except it insists on compiling
> the source first and I want to disable that. Without knowing where to
> look for possible additional targets, I woudn't be able to guess at
> them all.
>
> What I am interested in doing is having my regular build setup on the
> developer side and using Maven on the server side to generate the
> project documentation nightly. It seems that it would be a good idea
> to have the build side and doc side of Maven modular. I don't think
> the build side of Maven will fit my needs at this time. However, the
> documentation side will be a great benefit.
>
> How can I do documentation only? Where would I put the junit .xml
> reports so that they will get picked up and put into the documentation?
Hi Eric,
For your case, what I would do is :
- create a maven.xml file, in your project's directory.
- in that file, create an empty, <goal name="java:compile"
description="Does nothing !"/>
- in that file, add a <preGoal name="site"> that copies your junit.xml
file from wherever to ${maven.test.reportsDirectory}.
With this setup, the compiling phase would simply do nothing (the one in
your own maven.xml file is loaded after the plugins, and it will
override them),
and your test results will be copied to the test results dir before the
site is generated, so that it is processed and included in the final docs.
St�phane
>
> Thanks,
>
> Eric
>
>
>
> --
> To unsubscribe, e-mail:
> <mailto:[EMAIL PROTECTED]>
> For additional commands, e-mail:
> <mailto:[EMAIL PROTECTED]>
>
___________________________________________________________
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]>
