Glassfish v3 Source Code Managment

This page contains content on Glassfish v3 source code management topics.

cvs To svn Migration

The glassfish v3 team is in the process of migrating from cvs to svn. The main driver for this is the requirement to modularize the v3 glassfish workspace. This results in the following benefits.

• Small Footprint
• Fast Develop/Deploy/Test cycle
• Fast Startup
• User Profiles
  • Developer
    • Web
    • Java EE
    • Ruby
    • php
  • Enterprise Deployment
• Small Download

This modularization requirement involves the moving of many files. However, cvs does not have the capability to provide complete file history over these moves. Losing this history will make it more difficult to understand the evolution of a file. As a result, it will be harder to sustain the large glassfish codebase with the greater potential for functional and systemic regressions.

svn status

The conversion from cvs to svn has been completed. Browse the svn v3 glassfish repo for details. Click the trunk link to inspect the v3 trunk.

Future Plans

The current plan is to migrate from svn to hg a module at a time in CY 2008.

This page (revision-3) was last changed on 08-Nov-07 11:22 AM, -0800 by PaulSterk.
This page was created on 11-Oct-07 13:28 PM, -0700 by Paul Sterk.

More info...