You can use two basic approaches when translating this project structure to source control.
You can locate a project anywhere in the file system, though it is common to place it in the Eclipse workspace (.../eclipse/workspace/
). When you create a IBM® WebSphere® Portlet Factory project with WebSphere Portlet Factory Designer, all required sub-directories and files are created for you with the proper structure. The two approaches for translating a project structure to source control are:
Individual project approach
Each team member has a separate area in source control for their project artifacts (for example, models, Java classes and builders). The shape of this area should mirror the project structure.Shared Team project
This approach is useful if the projects have only loose coupling (for example, http connections). Artifact names should be chosen to avoid collisions if the created artifacts are to be brought more close together (in a common build). If there is to be a common build, a build process will be needed.
There is one shared source control area that captures all the artifacts created by the team members. This includes all source files, all generated files, and all WebSphere Portlet Factory shipping files (such as WARs). The shape of this area should mirror the project structure
This approach is useful when several people are working on different parts of one application. Each developer has a copy of WebSphere Portlet Factory and checks his work into a common source control area. Every team member can easily populate their project with all artifacts if necessary, and name collisions are easier to avoid.
In both cases, mirroring the structure of the project in source control allows easy traffic between your source control system and the project.
Parent topic: Your team development environment