Files and Folders for Source Control
Generally, you don't want to check in the compiled classes and libraries
for you Eclipse (or RAD) project. The Portlet Factory framework will
re-generate them for you. As a general rule, it is also not required
to check in the standard Portlet Factory project template files. The
best approach is to only check in project artifacts that are created after
the initial creation of the project.
There are various files and folders that you should consider
versioning in your source control system. Obviously your project
may include files and folders of your own which you are responsible for
3. any html pages, html
templates, style sheets, images, etc that you create in the project
check in the new .bdef files that you have created
- you may want to consider only specific configuration files which you
For example: domino_config contains the file default_domino_server.properties.
You should create your own property file (production_domino_server.properties).
default_domino_server.properties can be overwritten by Portlet Factory.
It is not recommended to modify files such as server.properties, cluster.properties,
etc. Instead, you should create an override.properties file and specify
the overridden values here.
You only need to check in the model files that you have created. The
base Portlet Factory models, such as those under the models/factory directory
need not be checked in.
profiles/.pset *- this directory may include profile sets from the
"solutions" that you don't need to save. They begin with
source - *Any Java projects which you have added*
lib - any
.jar files that you have added to the project
list is just the beginning of the list of standard Portlet Factory files
and directories. Maybe someone from IBM could help out here and make
this more complete and helpful. We need descriptions of what each
directory might contain