> Some explanations:
> -Let's use the term "plugin" in stead of "module".
> That's what they are,
> isn't it?
+1
> -Each component should provide their own
> documentation (xdoc).
+1
> -There will be one plugin for each DTD/XML

I think it would be too fine grained sometimes. In
JBOOSS module you will have to generate  at least 2
xml files - one for CMP and one for JBoss stuff. 
But basically idea is OK. 

Another question is intermodule dependency - jboss
does not make much sense wuthout EJB. It would need
some logic from there. 

> -Everything will be built by Maven (compilation,
> jarring...)
+1. Though I got problem with maven beta 7 - 
it just refuses to start ( but I hope I will sove it
soon )

> -There will be JUnit tests everywhere
+1
> So this is a proposal about a return to "one-module"
> CVS structure. What do
> you think about this?
+1

> I am working on a new ejb module using a structure
> similar to this, based on
> Velocity/XGG. The intention is that it will serve as
> a proof-of-concept and
> a template "best practice" structure for all the
> other plugins.

I'm waiting to see it in action. ( while hacking on
externalizer stuff :) )

regards,

=====
Konstantin Priblouda ( ko5tik )    Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >

__________________________________________________
Do you Yahoo!?
Faith Hill - Exclusive Performances, Videos & More
http://faith.yahoo.com


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Xdoclet-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/xdoclet-devel

Reply via email to