Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "PTP/sync-projects"
< PTP
(New page: === Synchronized Projects=== Information available after PTP 5.0 release will be placed here.) |
|||
| Line 1: | Line 1: | ||
| − | == | + | = Known Issues = |
| + | * Does not work well with projects that use Git for version control. Synchronization will use the same repository, littering it with automatic commits. A fix for this problem is slated for version 5.0.2. | ||
| + | * There are no wizards to convert existing projects to synchronized projects. A fix is planned for version 5.0.2. | ||
| + | * Errors occur during synchronization if the project contains files with odd characters, such as parentheses. (Files with spaces should work fine.) | ||
| + | * There are some potential pitfalls when configuring projects | ||
| + | ** Users should avoid changing configurations inside the new project wizard, as this will cause errors. Instead, add and change configurations after project creation. | ||
| + | ** The Workspace configuration only appears after the project is created. | ||
| + | ** The tool chain selected during creation is used for both the local machine and remote machine. Users need to adjust this after project creation. | ||
| + | ** For remote configurations, only the "Sync Builder" works, although other options are available (Project -> Properties -> C/C++ Build -> Tool Chain Editor). The "Sync Builder" is set as the default. | ||
| + | ** Attempting to change multiple configurations does not work correctly. | ||
| − | + | ||
| + | = Change Log = | ||
| + | |||
| + | === Version 5.0.1 === | ||
| + | |||
| + | * Sync empty directories | ||
| + | * Prevent users from modifying the synchronization properties of the Workspace configuration | ||
| + | * [https://bugs.eclipse.org/bugs/show_bug.cgi?id=349372 Fix bug 349372]: Build fails if empty environment variables are present | ||
| + | * Support managed project types | ||
| + | * Add Fortran synchronization wizard | ||
Revision as of 14:32, 1 July 2011
Known Issues
- Does not work well with projects that use Git for version control. Synchronization will use the same repository, littering it with automatic commits. A fix for this problem is slated for version 5.0.2.
- There are no wizards to convert existing projects to synchronized projects. A fix is planned for version 5.0.2.
- Errors occur during synchronization if the project contains files with odd characters, such as parentheses. (Files with spaces should work fine.)
- There are some potential pitfalls when configuring projects
- Users should avoid changing configurations inside the new project wizard, as this will cause errors. Instead, add and change configurations after project creation.
- The Workspace configuration only appears after the project is created.
- The tool chain selected during creation is used for both the local machine and remote machine. Users need to adjust this after project creation.
- For remote configurations, only the "Sync Builder" works, although other options are available (Project -> Properties -> C/C++ Build -> Tool Chain Editor). The "Sync Builder" is set as the default.
- Attempting to change multiple configurations does not work correctly.
Change Log
Version 5.0.1
- Sync empty directories
- Prevent users from modifying the synchronization properties of the Workspace configuration
- Fix bug 349372: Build fails if empty environment variables are present
- Support managed project types
- Add Fortran synchronization wizard