Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 109209

Summary:	[Project Sets] failure while importing team project set leaves wizard dialog up
Product:	[Eclipse Project] Platform	Reporter:	Rafael Chaves <eclipse>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	bh, eclipseeclectic
Version:	3.2	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:	stalebug

Description Rafael Chaves

2005-09-09 17:07:50 EDT

3.2 M1

If a failure happens while importing team project sets, the wizard dialog stays up.

To reproduce (on Windows), import a team project set once, open one file in of
the the projects just imported, and try importing again (confirming that you
want to overwrite the projects already imported).

Comment 1 Brett Hackleman

2006-02-21 17:50:22 EST

3.2 M5, Mac OS X 10.4.3

I'm also seeing this problem when importing a project set into a new workspace.  Loading the same project(s) manually via the CVS Repository works fine.

My projectSet.psf file:
========================

<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
	<provider id="org.eclipse.team.cvs.core.cvsnature">
		<project reference="1.0,:extssh:www.arsagilis.com:/cvs,Fitnesse/Fitnesse,Fitnesse"/>
	</provider>
</psf>

To reproduce:
================
1. Right click in Package Explorer -> Import -> Team -> Team Project Set -> Next -> Browse to file above, leave working set checkbox uncheckd -> C  Select the file above, then click next.  
2. Enter CVS password when prompted.
3. Wizard shows CVS server connection status, then returns to wizard screen.  
4. No error messages are displayed, but a closed project folder appears in the Package Explorer.  Opening the project manually reveals an empty project with a  skeleton .project file.

The stack trace in .log:
=========================

!ENTRY org.eclipse.ui 4 0 2006-02-21 15:34:50.858
!MESSAGE Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/Fitnesse]
!STACK 0
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/Fitnesse]
        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 2 Rick Mandel

2006-03-17 04:01:38 EST

I too have seen this problem with the M6 driver(eclipse.buildId=I20060223-1656 with java.fullversion=J2RE 1.4.2 IBM J9 2.2 Windows XP x86-32 j9n142-20050609 (JIT enabled)).  Additionally, I see the same failure when I Team -> Load Project Map.

This function worked fine on the M4 driver.  This should be a major regression

My Team Project Set file:
------------------------
<?xml version="1.0" encoding="UTF-8"?>
<psf version="2.0">
	<provider id="org.eclipse.team.cvs.core.cvsnature">
		<project reference="1.0,:pserver:eclectic.com:/cvsroot,com.eclectic.test,com.eclectic.test"/>
	</provider>
</psf>


Stack trace from the Error Log
------------------------------
java.lang.IllegalArgumentException: Attempted to beginRule: R/, does not match outer scope rule: MultiRule[P/com.eclectic.test]
	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 3 Michael Valenta

2006-03-17 08:59:03 EST

The problem mentioned in comment 1 and comment 2 was a problem introduced in M5 that has been fixed (the fix will be available in M6).

Comment 4 Eclipse Webmaster

2019-09-06 16:11:05 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

Comment 5 Eclipse Genie

2021-11-11 09:08:28 EST

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.