Community
Participate
Working Groups
We are currently using a PRE_AUTOBUILD listener to handle the 1.0 .vcm_meta file. If 1.0 to 3.0 project compatibility is a requirement, we need to leave this in. However, PRE_AUTOBUILD may not work anymore so we could potentially need to modify how we convert the .vcm_meta into a .project. Hopefully, 1.0 t0 3.0 is not a requirement and the support can be removed.
The answer is to remove the old code and provide an entry for the porting guide which describes the change, why it was made and how the user can get around the problem (i.e. if upgrading from 1.0 to 3.0, start 2.x on the workspace to ensure that the .vcm_meta is translated to a .project).
The following should be included in the 3.0 readme (instead of the porting guide). CVS and the Eclipse 1.0 .vcm_meta file. Support for the .vcm_meta file has been removed from Eclipse 3.0 because changes to the builder mechanism make it a considerable amount of work to support this Eclipse 1.0 functionality. This will only impact customers who are migrating projects created using Eclipse 1.0 directly to Eclipse 3.0 without involving Eclipse 2.0. The workaround to avoid problems is to migrate the projects to an Eclipse 2.0 workspace, commit the newly created .project file to the repository and them migrate to Eclipse 3.0. If this is not done, the projects will loose their meta information, such as project nature (e.g. Java project) and associated builders.
added to 3.0 release notes.
