Re: [Statsvn-developers] StatSCM Maven 2 Mojo.

[Benoit X. <bx...@ob...>]

Doug,

You can place the XDOC in target/generated-site/xdoc/YOURDIRECTORY

This will be converted to html in target/site/YOURDIRECTORY
Another not-fully-documented-feature...

Have a look at http://qalab.sourceforge.net/

Good luck and let me know

Benoit

PS: do not forget that the statsvn packages are going to move around... ;-)

-----Original Message-----
From: sta...@li...
[mailto:sta...@li...] On Behalf Of Doug
Culnane
Sent: 18 November 2006 19:42
To: sta...@li...
Subject: [Statsvn-developers] StatSCM Maven 2 Mojo.

To keep the communication and enthusiasm going here is an update.  I have
set up the StatSCM Maven 2 Mojo project. 
http://stat-scm.sourceforge.net/

I have got past the hello world stage but it seams that the Reporting Mojo
Interface is a lot more Java and less script to implement.
Therefore I have a lot of playing around to do before I  understand the best
way to implement this.  This all seems to be very new and the Documentation
is still // TODO or keeps changing (by the hour at the moment).  Luckily
there is plenty source out there to copy.

I still have to understand the best way to handle the xdocs. 
Unfortunatly is is not a case of placing them in "target/generated-xdocs".
folder seems to have moved to ./xdocs which is not ideal.?...

I have remove the source of StatSVN form a svn:external link to a dependancy
so that I can control StatSVN (and StatCVS) versions more easily.

My plan of attack is
- get the handling of xdocs right and as Maven 2 integrated as possible.
- get the log file automatically.
- Implement date ranges and other configuration options.
- Write HowTos and other Docs for site.
- Have a look as implementing CVS.

I will release my stuff under MIT license so that it has more chance of
going further into the Mojo project.

Comments welcome (especially Positive ones ;-) ).

BTW.  (2 more Euro cents) If you use Jelopy then it always does all files.
Therefore it needs to be bound into the build lifecycle so that only new
code is changed.  This only works well if all agree on the "standard", the
standard is centralized and every one uses the same build before they check
new code in.  It is definitely a solution and make code formating a no
brainier but it may be too much pain for not much gain...

All the best,

Doug




-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's
Techsay panel and you'll get the chance to share your opinions on IT &
business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Statsvn-developers mailing list
Sta...@li...
https://lists.sourceforge.net/lists/listinfo/statsvn-developers

--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.14.7/537 - Release Date: 17/11/2006
17:56
 

-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.5.430 / Virus Database: 268.14.7/537 - Release Date: 17/11/2006
17:56