I think there are a lot of things that still need to be recommended (including the indenting ;). How about starting a list of things? There a few I added wrt the javadocs, but I'm not entirely sure I've picked the right names or everything that's required...
J. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Friday, 05 October 2001 9:44 pm > To: [EMAIL PROTECTED] > Subject: Re: Build.xml standardization > > > > General questions: (sorry if this is a dup) > > - If the tests are java classes that are separated from the source, is > there an interim location where the test.class files should live? Or > should then just go willy-nilly in check.dir along with test > results, etc.? > > - For projects that have XML documentation sources that are checked in, do > we have a variable for where they live? I.e. Xalan has xdocs.dir > = ./xdocs > which is where we check in .xml files that get transformed into whatever > sort of user docs into docs.dir, docs.user.dir, etc. etc. > > - Do you want to have a default variable for the actual name of output > distribution units .zip/.tar.gz? This would be useful for Gump, so it can > just post these directly to some standard nightly posting > location, without > Sam having to have custom copy code for each project. For example: > <property name="dist.file" value="${name}-j_${version}"/><!-- GUMP: > actual path/name of dist target .tar.gz/.zip--> > > Overall the build.zip(.xml) being passed around looks good, except for the > indenting... ;-> > > - Shane > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
