I want to get some feedback on how other developers handle the management of certain common files across multiple project trees.
I am developing about a dozen different web modules right now, each with its own project tree. However, certain resources are used in all of the projects, such as build.xml and build.properties. I would like to keep these files in CVS, but I don't want the files duplicated in every single CVS module because a change to one would still require a syncronization across all the projects. At the same time, I want the project tree to be able to stand alone so that it isn't dependent on a "common" folder. My question is, where do I store it and how do I get the most recent version? The response I most anticipate is to have a target in build.xml that reaches out to a common directory and pulls the newest version into the project tree. Then the common folder will have its own CVS module and all updates to such common files should occur only in the common folder and not on the file inside of the particular project which uses it. Running the target allows a project tree to be brought "up to date" ready for export as a standalone project tree. Am I on the money or is there a better way to handle such resources? Dan -- Open Source Advocacy http://www.mojavelinux.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
