Issues with the Eclipse Projects and Files

Projects

• If you are upgrading your license from Enterprise Developer for Eclipse Personal Edition (v2.2 or earlier) to Enterprise Developer, or from Enterprise Developer Connect (v2.2.1 or later) to Enterprise Developer, any existing projects compiled to either .exe or .dll files using the old license must be updated in order to recreate the .cobolBuild file. You can do this done by adding or removing files from the project or by deleting the .cobolBuild file. Updating the project in this way ensures Eclipse will fully build the executable files.

• Opening a COBOL or a PL/I project in Enterprise Developer modifies the .cobolProj and .pliProj files. Once modified the .cobolProj and .pliProj files are no longer backward compatible with older versions of Enterprise Developer. This prevents you from opening the same projects in earlier versions of Enterprise Developer.
  Note: Micro Focus recommend that you backup your .cobolProj and .pliProj files before opening projects created in earlier versions of Enterprise Developer.

Symbolic files

• Modifying the target of a symbolically linked COBOL source file does not force a recompile of the program when refreshed in the Eclipse IDE. In addition, if the file is open in an editor while the target linked source file is edited then the changes are not automatically refreshed in the editor. Micro Focus recommends that you do not use symbolically linked files with Eclipse projects.
  Note: This applies to both Windows and UNIX environments.