Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 128718 - Import Team Project Set not working
Summary: Import Team Project Set not working
Status: RESOLVED DUPLICATE of bug 128707
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 critical (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-20 15:38 EST by Roy Paterson CLA
Modified: 2006-02-20 15:50 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roy Paterson CLA 2006-02-20 15:38:16 EST
Eclipse 3.2 M5

The Import Team Project Set functionality appears to have been broken in the M5 release.  This function worked in Eclipse 3.2 M4.

When I click "finish" in the "Import a Team Project Set" dialog, only one project from the set is created.  The project has the right name but it is closed, and when I open it the project is empty except for a bare-bones .project file with no natures or builders.  

<?xml version="1.0" encoding="UTF-8"?>
<projectDescription>
        <name>MyProject</name>
        <comment></comment>
        <projects>
        </projects>
        <buildSpec>
        </buildSpec>
        <natures>
        </natures>
</projectDescription>

The "Import a Team Project Set" dialog does not close - you have to push the cancel button to get rid of it.  The Team Project Set file (.psf) seems to have identical content to the one generated in Eclipse 3.2 M4, so I assume the "export" is working OK, it's just the "Import" that is broken.

Two errors appear in the error log:

!SESSION 2006-02-20 14:24:26.033 -----------------------------------------------
eclipse.buildId=I20060217-1115
java.fullversion=J2RE 1.4.2 IBM Windows 32 build cn1420-20040626 (JIT enabled: jitc)
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments:  -os win32 -ws win32 -arch x86 -data my_workspace

!ENTRY org.eclipse.ui 4 4 2006-02-20 14:25:20.993
!MESSAGE Unhandled event loop exception

!ENTRY org.eclipse.ui 4 0 2006-02-20 14:25:21.023
!MESSAGE Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/MyProject]
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/MyProject]
	at org.eclipse.core.runtime.Assert.isLegal(Assert.java:58)
	at org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:116)
	at org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:225)
	at org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:58)
	at org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:218)
	at org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java:96)
	at org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace.java:1681)
	at org.eclipse.core.internal.resources.Project.open(Project.java:832)
	at org.eclipse.core.internal.resources.Project.open(Project.java:890)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseFolder.mkdir(EclipseFolder.java:115)
	at org.eclipse.team.internal.ccvs.core.client.ResponseHandler.createFolder(ResponseHandler.java:80)
	at org.eclipse.team.internal.ccvs.core.client.StickyHandler.handle(StickyHandler.java:67)
	at org.eclipse.team.internal.ccvs.core.client.Request.executeRequest(Request.java:218)
	at org.eclipse.team.internal.ccvs.core.client.Command.doExecute(Command.java:404)
	at org.eclipse.team.internal.ccvs.core.client.Checkout.doExecute(Checkout.java:159)
	at org.eclipse.team.internal.ccvs.core.client.CheckoutWithOverwrite.doExecute(CheckoutWithOverwrite.java:52)
	at org.eclipse.team.internal.ccvs.core.client.Command$1.run(Command.java:323)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseSynchronizer.run(EclipseSynchronizer.java:1450)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseResource$2.run(EclipseResource.java:260)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1733)
	at org.eclipse.team.internal.ccvs.core.resources.EclipseResource.run(EclipseResource.java:257)
	at org.eclipse.team.internal.ccvs.core.client.Command.execute(Command.java:335)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability$1.run(CVSProjectSetCapability.java:378)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1733)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability.checkout(CVSProjectSetCapability.java:406)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability.checkout(CVSProjectSetCapability.java:288)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability$LoadInfo.checkout(CVSProjectSetCapability.java:226)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability.checkout(CVSProjectSetCapability.java:167)
	at org.eclipse.team.internal.ccvs.core.CVSProjectSetCapability.addToWorkspace(CVSProjectSetCapability.java:119)
	at org.eclipse.team.internal.ui.ProjectSetImporter.importProjectSet(ProjectSetImporter.java:84)
	at org.eclipse.team.internal.ui.wizards.ProjectSetImportWizard$1.execute(ProjectSetImportWizard.java:65)
	at org.eclipse.ui.actions.WorkspaceModifyOperation$1.run(WorkspaceModifyOperation.java:100)
	at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1733)
	at org.eclipse.ui.actions.WorkspaceModifyOperation.run(WorkspaceModifyOperation.java:112)
	at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:113)
Comment 1 Michael Valenta CLA 2006-02-20 15:50:26 EST

*** This bug has been marked as a duplicate of 128707 ***