I think this is a good idea, but we need to sort out a few issues: 1) I suppose you mean moving the whole xdoclet module to jboss. 2) If my assumption is right on 1), we must update our build system to get the sources from jboss when building. I guess we still want the maven-generated site to include the jboss documentation. -Or would a link be ok? 3) As the core evolves, so must the jboss module. The jboss module's build should continuously integrate with the core. 4) We need to decide what's the right time for this. Right after 1.2 relese, or when XDoclet 2.0 (velocity) is up and running? 5) If we go for this approach, should we encourage other "spi" projects to do the same, so we can focus on the core? 6) We must provide strict guidelines, so we can continue to define a set of common cross-container tags like @ejb-persistence etc.
Aslak > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of > [EMAIL PROTECTED] > Sent: 19. september 2002 21:49 > To: [EMAIL PROTECTED] > Subject: [Xdoclet-devel] DISCUSSION: removing JBoss tags > > > 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 ------------------------------------------------------- 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
