Our sub-components has its own project and its own source directory. That's the way our SourceSafe hierarchy was set up--so that's how the sources are fetched before a compile.
-----Message d'origine----- De : David McTavish [mailto:[EMAIL PROTECTED]] Envoyé : 26 novembre, 2002 12:55 À : 'Ant Users List' Objet : RE: Naming build files i agree. -----Original Message----- From: Dominique Devienne [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 12:18 PM To: 'Ant Users List' Subject: RE: Naming build files If your sub-components are part of the same src/ directory, then most likely you should have a single build.xml for all of them. But that's just me. --DD -----Original Message----- From: Patricia Watt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 11:16 AM To: Ant Users List Subject: RE: Naming build files When Dominique said there's usually a single build file per project, I take that "project" to mean a component. As I said, we have several independent component/projects that use the same jar(s) (sub-components). I do not want to have to repeat what's in the build files for the sub-component jars in each of the build files for the independent components. So I think we'll stick to the practice of having build files for the sub-component jars. And based on other responses, apart from the main build file for an independent component (which IS usually called "build.xml"), it doesn't seem anathema to use other names for other ant scripts--like those for our sub-components. Thanks for the replies, Tricia -----Message d'origine----- De : Dominique Devienne [mailto:[EMAIL PROTECTED]] Envoyé : 26 novembre, 2002 11:43 À : 'Ant Users List' Objet : RE: Naming build files Be careful, Ant scripts are not makefiles... A friend embedded over 80 build files in his source tree, because he was used to makefiles. One usually has a single Ant build script per project, most often at the root of the project. Since build.xml is the default Ant build script, one doesn't have to specify the -f or -buildfile switch on the command line. Putting the Ant build script at the top level is important, as everything can then easily be defined relatively from this point (see the location attribute of <property>). Does that help? --DD -----Original Message----- From: Patricia Watt [mailto:[EMAIL PROTECTED]] Sent: Tuesday, November 26, 2002 10:39 AM To: Ant Users List Subject: Naming build files Hi, A fellow here at my work seems to think it's desirable (best practice) that all build files are named simply "build.xml". And hence that they'd have to be stored in appropriately named directories in the source hierarchy. Any opinions on this? Thanks for any comments. Tricia -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
