This tool can be used to add thousands of files and directory in perforce server on single click which is having different-different hierarchy
Java should install and class path should set.
Put the code under ClientSpec root folder in the same hierarchy which you want to add in perforce server.
Create a changelist first. Just go to command prompt and type “p4 change”. Perforce will automatically create a changelist and will give you the changelist number. It will also ask you to update a text file with the changelist description. Just give the appropriate description there. Note the changelist number.
The file file has one file called “config.properties”. So first update it with two values. The changelist number and the source path. The source path can be “D:/Perforce/Components/DatabaseServer”.
Use forward slash only “/”.
Step4: Once these files are updated, you can run the script file “makescript.bat” which will update the “checkinscripts.bat” with new checkin scripts.
Step5: Run “checkinscripts.bat” and refresh perforce console. See that new folder is created below components folder and the files are inside
Note: The file which will not be added into perforce server can be found in “missedfiles.log”
Share common projects with two different projects in CVS If there are two or more projects in the repository, some of the files are common in these two projects and some are different.How to share the files that are same between these projects? How can archive this? How Changes in common files be reflected to both projects. Version of CVS 2.5.03
Answer: The CVSROOT/modules2 file or the older CVSROOT/modules file can help with this sort of thing:
Generally the best CM independent solution is to organise your project source code hierarchy within the CM tool in such a way that ‘common’code is in a project/module/directory of it’s own so it can be checked out and managed independently of other projects, ie:
Then you define a module where ‘projecta’ = ‘proja’+’common’ so when a person does ‘cvs co projecta’ they get:
If your server is running on Linux then you can ‘cheat’ by simply symbolically linking the RCS file into two directories (though this may cause locking conflicts if the files are very busy).
Thanks to:Arthur Barrett