|
From: Hans B. <ben...@ch...> - 2003-06-11 11:35:11
|
I had to change the CVS substitution mode for babeldocconvention.xml, because jalopy complained about unexpected characters in end tags (?!?). Now it works again. I also added "The Apache Software License" to the keys for headers that should be removed, because otherwise the header will be added again and again... This makes the $Log$ keyword in this header somewhat useless, but it tends to give problems with branch merges, anyway. Regards, Hans On Tue, 10 Jun 2003, Bruce McDonald wrote: > Hans, All: > > Thank you Hans! This is just what is needed. I have gone ahead and updated > your convention.xml to place the APL header on each of the java source files. > I have also remove those separator characters. I have run this on the init > source files and I will commit them so that you can look at the results. > Please comment. > > regards, > Bruce. > > On Tuesday 10 June 2003 12:17 pm, Hans Benedict wrote: > > On Tue, 10 Jun 2003, Dejan Krsmanovic wrote: > > > Hans, could you add jalopy task to build.xml file (files)? Libraries for > > > jalopy should be stored under support folder since they are not needed at > > > runtime. > > > Task should be optional - it should not be executed by default. > > > > O.k., I put it into CVS. The new task is called "format". At the moment it > > is actually only used for the soap module, because there will be some > > problems in the beginning, mainly concerning javadoc comment. For example: > > jalopy crashes in SqlEnrichPipelineStage due to an "<a href=..." in the > > @author tag. > > > > I suggest that everybody tests the modules he feels responsible for (;-)) > > by removing the comment in the corresponding build.xml. > > > > I left in the "destdir"-attribute, which means that the modified > > files go to ./tmp/format. If you are happy with the result, please remove > > the line with the destdir attribute, so that the source files get > > overridden, and then recommit the files to CVS. > > > > I also found, that jalopy takes rather a long time to parse something in > > core/journal, but I have no idea, what is happening there. > > > > Bruce, the header text lives in support/jalopy/babeldocconvention.xml. If > > you change it there, it can be changed in the source files as well. You > > can either change it manually or use ./support/jalopy/bin/preferences.sh > > (It seems, there is no commandline argument for the file, so you will have > > to use the Import/Export buttons.) > > > > Good luck, > > Hans > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > > thread debugger on the planet. Designed with thread debugging features > > you've never dreamed of, try TotalView 6 free at www.etnus.com. > > _______________________________________________ > > Babeldoc-devel mailing list > > Bab...@li... > > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > > > ------------------------------------------------------- > This SF.net email is sponsored by: Etnus, makers of TotalView, The best > thread debugger on the planet. Designed with thread debugging features > you've never dreamed of, try TotalView 6 free at www.etnus.com. > _______________________________________________ > Babeldoc-devel mailing list > Bab...@li... > https://lists.sourceforge.net/lists/listinfo/babeldoc-devel > |