#TFS as an External Tool
hurr
untested and still refers to original example tha used cvs. don't use (yet).
source: https://apex.oracle.com/pls/apex/f?p=43135:28:11686443451696::NO::P28_ID:381
sqldevtfs.bat:
::This is a windows batch file but conversion to a shell script is trivial.
::All it does is change directory to the source file directory and issue a commit.
@echo off
pushd %1
cd
echo cvs commit -m%3 %2
cvs commit -m%3 %2
popd- Goto Tools > External Tools
If this is the first time you have used the dialog, you will be prompted to set up some automatic definitions.
- Click on New and fill in the fields as follows
- Program Executable:
- Arguments:${file.dir} ${file.name} "${promptl:label=Checkin comment} "
The quotes round the final parameter are necessary because if can contain spaces. If your pathnames or file names contain spaces, the other parameters will need to be quoted too.
- Run Directory:
- Click Next As of build 2197 there are a couple of error dialogs to click through at this stage. They don't seem to affect the functionality.
- File in the display options as appropriate.
- Click Next
- File in the Integration options as appropriate. I haven't experimented with these, but you should have at least the tools menu selected. You should probably also check the Reload Open Files box.
- Click Next
- File in the Availability options as appropriate. I have set Enabled to Always for simplicity.
- Click Finish
- Only works on one file at a time
- Only works on FILES, not other object nodes.
- No access to the database. In the case of PL/SQL files I would like to be able to resubmit them to the database after checkin (so that the checkin comments and version numbers are up to date in the database. The external tools interface doesn't reliably provide connection details to allow this.
- You can replace the commit command with other cvs commands, or you can make the cvs command a prompted parameter.
- You can replace cvs with another version control tool.