| Summary: | Import of information projects from a different workspace does not work | ||
|---|---|---|---|
| Product: | z_Archived | Reporter: | Joerg Reichert <joerg83reichert> |
| Component: | Remus | Assignee: | Tom Seidel <tom.seidel> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| Whiteboard: | |||
|
Description
Joerg Reichert
(In reply to comment #0) > Build Identifier: RCP-TRUNK-113 > > The projects are imported as empty category folders and the following error > dialog is shown: > 'Building workspace' has encountered a problem > > Errors occurred during the build. > Errors running builder > 'org.eclipse.remus.core.internal.builder.InformationBuilder' on project > 'Gemeinsam'. > java.lang.NullPointerException > > When I am using switch workspace and redirect to the other workspace, the > information structure is shown correctly. But the import of a information > project does not work. I guess there is a issue with the metadata. Maybe it > also something to do with different RIM versions, as the first workspace is > created by an older version. > > Reproducible: Always Yes as part of the migration to Eclipse all namespaces has changed from org.remus.infomngmnt to org.eclipse.remus including the metadata of the project. A possible workaround is to share your data with a local file repository. In the new version it should be possible to synchronize these old elements with the current version. Backward-Compatibility to workspaces using the old namespace (before becoming an Eclipse project) is out of scope. I could import my old data via the proposed shared local file repository, so migration to the new version was no problem. |