XDocleteers, There is a push to get the JBoss XDoclet tags under JBoss-CVS. This would represent a shift in ownership/responsibility/location of all the JBoss-specific tags/tasks/templates to the JBoss project.
It may sound a little distressing at first, but in reality, it is a major win for XDoclet. The basic argument *for* moving JBoss module to JBoss-CVS comes down to one question, 'Why does XDoclet have any custom, vendor-specific modules?' Answer: because the vendors didn't care/know anything about XDoclet and wouldn't/couldn't/didn't-know-how-to supply their own tags! Well, JBoss is all over XDoclet. It is used in generating JMX components and in the test-suite. With the move to JBoss, the tags will be versioned with the appropriate releases of JBoss (extremely important as JBoss goes to 24x7x365 support). When users download JBoss, they will get a JBoss module that supports their version of JBoss. It also allows the JBoss developers to keep the JBoss module up-to-date with the latest changes to JBoss. JBoss developers will now be *required* to develop/maintain JBoss tags as they add/remove/change features of JBoss. Another not-so-obvious point is exposure. JBoss gets an average of 150,000+ downloads a month (~208,000 in 04/02). They have users with CD subscriptions, Marc Fleury regularly gives briefings to Java User Groups, advanced training occurs almost twice a month all over the world, ... JBoss is the hottest thing since sliced bread! Now, everywhere JBoss goes, XDoclet will be taught as the way to develop EJBs! Thoughts? Michael ------------------------------------------------------- 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
