I'm willing to make the TOC and do some work on the docs. For the logo: I think we decided on keeping the current one, no?
For the build scripts: we should have one common build script for all the modules, and the modules just import this. They can override targets if needed. This is the same approach of the jakarta taglibs project, where you can build all taglibs with one common.xml build file. Mathias ----- Original Message ----- From: "Aslak Helles�y" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Sunday, April 28, 2002 3:23 AM Subject: [Xdoclet-devel] RE: Build > Hi! (took this back to dev) > > Good news! The BCEL/Bootstrapper stuff will go away now that Erik has > finally got a yes from his Ant team to support creation of dynamic elements > natively in Ant. This is now being used in DocletTask on > MODULE_REFACTORING_BRANCH. > > D O C U M E N T A T I O N > > The module structure is ready (on MODULE_REFACTORING_BRANCH), so now we can > start splitting up the xtags.xml from xdocletgui and put the pieces under > their approriate modules. I suggest we do it like this: (using jboss as an > example): > > /xdoclet/modules/jboss/src/xdoclet/modules/jboss/ejb/resources/xtags.xml > /xdoclet/modules/jboss/src/xdoclet/modules/jboss/jmx/resources/xtags.xml > /xdoclet/modules/jboss/src/xdoclet/modules/jboss/web/resources/xtags.xml > > Doing it this way lets us separate unrelated tags from the same vendor. It > would be nice to be able to avoid mixing up the description of jboss' jmx > tags, web tags and ejb tags. Having it under resources also makes it easier > to incorporate it in the jar file. It will be needed when the xtags > validation code enters the scene. > > The xsl in xdocletgui can be applied to these xtags.xml files wherever we > put them, and generate an HTML document for each of them. This results in > more fragmented docs, and is better I think. We also need to make some TOC > menu which will point to these HTML files. This should also be automatic. > Any ideas about how to do that? I also suggest that the generated HTML files > be put in a directory structure where they all reside in a different > directory. Then they can all be called doc.html or something, and we needn't > worry about names. > > V E R S I O N > > I'm not 100% sure if we haven't broken any backwards compatibility anywhere, > so perhaps we should version it 2.0.beta? > > L O G O S > > What happened to all the nice logos different people submitted? As far as I > remember, we didn't reach consensus about which one to use. Can somebody > pleas put them back so we can have a proper vote on that? We should try to > get it in for the release. > > T E A M W O R K > > There is a lot to do now, so let's all put in an effort to get out this beta > releas of xdoclet 1.2 (or is it 2.0)! Currently here is who's working on > what: > > New build scripts: Vincent > Move templates: Ara > Upgrade to Ant 1.5: Aslak > Make docs: ??? > Put back logos and make a poll session on SF: ??? > > The biggest job is the new build scripts and making the docs, so we need > more people to join in here. Hey, we're 13 committers, so it shouldn't be a > problem. > > Cheers, > Aslak > > > -----Original Message----- > > From: Vincent Harcq [mailto:[EMAIL PROTECTED]] > > Sent: 28. april 2002 10:55 > > To: Ara Abrahamian; Aslak Hellesoy > > Subject: Build > > > > > > I've done the build scripts for "ejb" and "bea" using aslak's trick > > Look in script/ > > There is an "abstract" pre and post target to add custom target (xmlrpc) > > > > I have also move aslak modules/build to modules/script > > This will call all modules build to create each modules jars > > > > Each modules can still be run one by one if needed. For that I > > did not put > > the build.bat, ... Using ant.bat (with ANT_HOME set and ANT_HOME/bin in > > PATH) is enough IMHO. In fact we should avoid having build.bat > > everywhere, > > calling "ant" should work ok no ? > > > > Looks very nice now. Here are some issues I also think we should debate: > > -Using ant's batch script for running ant puts only the bare necessities on > the system classpath. It seems that if xdoclet.jar is not on the system > classpaht, the detection of xdoclet.jar's location doesn't work. See > xdoclet.loader.ModuleFinder for more details. We need to solve this in order > to get the dynamic module lodaing to work. > > -We can rely on people using XDoclet from CVS to have Ant installed, but > should't rely on the users to have it. Ant 1.5 should be in the distro. > > -The samples should still have build.bat and build.sh. It should be a > no-brainer to execute the samples out of the box. > > -People will use samples' build.xml as a template for their own build > script, so I think we should avoid using the include feature here. > > -We should provide a binary distro without xdoclet's source code (and avoid > including any of the jars that are only required to build xdoclet). > > -We should provide a src distro which looks exactly like CVS so people > withot CVS access can build themselves (and fix bugs/program modules). > > > Next steps is to build the "distri", > > See you later > > Vincent > > > > > _______________________________________________ > Xdoclet-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/xdoclet-devel > _______________________________________________ Xdoclet-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-devel
