REPOTOOLS Is there a detailed list of all options?
Accepted answer
Hello Mark
I agree that the repotools has hardly any documentation in the public documentation, we need to improve it.
I use the following workaround, I am not sure if you too would like it.
I usually run the repotools-<appName>.bat and point it to a txt file to get all the possible arguments, that could be used. Not the best option, but very handy option to get all the possible options.
Eg:
Using the command prompt, cd to <Install_dir>\server directory
run the command "repotools-jts.bat > repotools-JTS_options.txt"
the resulting file that will be created in the server directory will have all the arguments.
Although the documentation is not detailed, the listing is pretty self-explanatory. You would want to repeat this to other apps to get application specific arguments.
I agree that the repotools has hardly any documentation in the public documentation, we need to improve it.
I use the following workaround, I am not sure if you too would like it.
I usually run the repotools-<appName>.bat and point it to a txt file to get all the possible arguments, that could be used. Not the best option, but very handy option to get all the possible options.
Eg:
Using the command prompt, cd to <Install_dir>\server directory
run the command "repotools-jts.bat > repotools-JTS_options.txt"
the resulting file that will be created in the server directory will have all the arguments.
Although the documentation is not detailed, the listing is pretty self-explanatory. You would want to repeat this to other apps to get application specific arguments.
2 other answers
Any updates on the public documentation of repotools?
Thanks
Thanks
Comments
Clear documentation is imperative. A couple of problems we found (undocumented):
1. Not all options work with all versions, something that was introduced in one version many no longer work in a subsequent version. In fact, it makes not sense to have the option available. The team seem to have a problem obsoleting options.
2. It doesn't always do what you expect, make no assumptions about the tool and the options, we've been caught out before expecting it to do one thing, but having it do another.
Clear documentation would have alleviated some of the problems we've had, however, I'd like to see a better tool.