Display changes to configuration for the specified deployed bundle.
bw cfgdiff PATH [FILE [OLDREV [NEWREV]]] (or NAME cfgdiff [FILE [OLDREV [NEWREV]]])
- PATH points to a deployed bundle (not needed when action is called using the deployed bundle's NAME)
- FILE is the name of a configuration file inside that deployment. If not specified, all configuration files are shown.
- OLDREV is the number of the old revision to compare. If not specified, the latest revision is used.
- NEWREV is the number of the new revision to compare. If not specified, the local copy of the configuration file is used.
<bw.cfgdiff path="${path}" [config="${config}" [oldrev="${oldrev}" [newrev="${newrev}"]]] />
# Show all differences for all configuration files for the current tomcat
tomcat cfgdiff
# Show all differences since revision 2 of server.xml for the current tomcat
tomcat cfgdiff server.xml 2
# Show the differences between revision 4 and 5 of helloserver.properties
# for a specific deployment of the helloserver bundle
bw cfgdiff /local/dev/helloserver helloserver.properties 4 5
- BundleWorks checks for changes to configuration each time a deployed bundle is started or run.
- The attribute Runtime-Config inside the bundle info file determines which files are checked.
- The version of a configuration file inside the work directory may be different that the latest one inside the configuration archive if the file was changed after a start. In this case, the cfgdiff will list a revision called "local copy".
- The cfghistory commmand can be used to see a summary of revisions for a particular configuration file.