Copying build settings between projects

because we use subversion, im constantly creating new projects for each branch (we branch approximately monthly) Is there a quick and easy way copy all my build settings (classpaths, excludes) from one project to another?

if a solution existed i would be very VERY happy.

4 comments
Comment actions Permalink

Copy the project and module files to the new branch, they use relative paths so everything should just work. If you check these into svn you wont need to do this at all

0
Comment actions Permalink

project - .ipr modules - ]]>.iml

0
Comment actions Permalink

Chris Sherratt wrote:

Copy the project and module files to the new branch, they use relative paths so everything should just work. If you check these into svn you wont need to do this at all


When I check a project file into Perforce, IDEA natters at me about it
being read-only. This happens even if I haven't attempted to modify the
project. Do I need to make the project file (and perhaps the module
file(s)) writable, even though they aren't checked out? That isn't the
usual practice, at least not around here.

0
Comment actions Permalink

IDEA probably writes changes you make to your project and/or modules to the corresponding files and therefore expects to be able to write to these files. This is no problem if you use cvs or svn since they do not use explicit checkin/checkouts with readonly locks.
Nevertheless, in my team we store 'template' project files in the repository but copy these files before use and let IDEA work with these copies instead. This gives you more control when to check in changes you made to these files resp. which changes to adopt that were made by others. you can use two simple ant tasks 'update from template' and 'derive template' that accomplish the copy process.
just an idea.

welo

0

Please sign in to leave a comment.