Setup Development Use Case

Switch branch for build.xml.
1. Right-click on build.xml.
2. Go to "Team" sub-menu.
3. Go to "Switch to another Branch/Tag/Revision..."
4. Replace "trunk" with "branches/vendor-trunk".
Complete the same steps for:
- build.properties.xml
- build-foundation.xml
- log4j.properties
- work/web-root
- work/db/scripts/rsmart
- work/src/META-INF
- work/src/com
- work/src/org (this step will take longer than others)
- all files (exclude the folders, configuration.properties and spy.properties) in work/src
- test/lib
- test/infrastructure/src/org
- test/unit/src/com
- test/unit/src/org
- test/integration/src/org
- all folders and .jar files in the build folder (you can select all of them at once)
- distribution
Run dist-local.

"svn:externals v. Branching

Externals is good for linking source code from another repository, so that when an export or checkout of source code happens, dependency code is also retrieved. This is mostly good with development. For example, linking kfs-cfg-dbs, kul-cfg-dbs, and kfs together to be retrieved in the same checkout.

It is not useful when there is an expectation of overlap between the trunk and the external repository. The idea behind externals is that it is completely separate; therefore, there can be no overlap.

Setup Development Use Case

Switch branch for build.xml.

Right-click on build.xml.

Go to "Team" sub-menu.

Go to "Switch to another Branch/Tag/Revision..."

Replace "trunk" with "branches/vendor-trunk".

Complete the same steps for:

build.properties.xml

build-foundation.xml

log4j.properties

work/web-root

work/db/scripts/rsmart

work/src/META-INF

work/src/com

work/src/org (this step will take longer than others)

all files (exclude the folders, configuration.properties and spy.properties) in work/src

test/lib

test/infrastructure/src/org

test/unit/src/com

test/unit/src/org

test/integration/src/org

all folders and .jar files in the build folder (you can select all of them at once)

distribution

Run dist-local.