AW: [Subclipse-users] Subclipse 1.3.15 does not allow to update a workingset on eclipse 3.4

The Problem persists with subclipse 1.3.16
and Eclipse M7 (I20080502-0100)

We cannot update any project with subclipse.
We have to update with Tortoise SVN and then refresh the eclipse workspace.

Thanks
Roland Gradenegger

(I can reproduce this with 2 new projects and only 1 empty class in each)

-----Ursprüngliche Nachricht-----
Von: Gradenegger, Roland
Gesendet: Donnerstag, 15. Mai 2008 14:42
An: users_at_subclipse.tigris.org
Betreff: [Subclipse-users] Subclipse 1.3.15 does not allow to update a workingset on eclipse 3.4

Betreff: Subclipse 1.3.15 does not allow to update a workingset on
eclipse 3.4

We have two Workingsets with different branches (different project-names
too)
of an allmost identical application.

eg. one workingset is "production" and the other is "unstable"
(I do not think that this causes the error, this is only additional
info)

When I am trying to update either the whole workingset or even only one
project from svn,
then the following error occours.
(info: unst-appli and unst-ostpr are two projects of the same
workingset)

Environment info:
================
OS: Windows XP
Eclipse Version: 3.4.0, Build id: I20080330-1350
SubClipse: Tag 1.3.15
Using: JavaHL
Protocoll: svn://

StackTrace:
==========
java.lang.IllegalArgumentException: Attempted to beginRule:
P/unst-appli, does not match outer scope rule: P/unst-ostpr
        at org.eclipse.core.runtime.Assert.isLegal(Assert.java:62)
        at
org.eclipse.core.internal.jobs.ThreadJob.illegalPush(ThreadJob.java:122)
        at
org.eclipse.core.internal.jobs.ThreadJob.push(ThreadJob.java:232)
        at
org.eclipse.core.internal.jobs.ImplicitJobs.begin(ImplicitJobs.java:58)
        at
org.eclipse.core.internal.jobs.JobManager.beginRule(JobManager.java:230)
        at
org.eclipse.core.internal.resources.WorkManager.checkIn(WorkManager.java
:117)
        at
org.eclipse.core.internal.resources.Workspace.prepareOperation(Workspace
.java:1747)
        at
org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:
1467)
        at
org.tigris.subversion.subclipse.core.client.OperationManager.endOperatio
n(OperationManager.java:118)
        at
org.tigris.subversion.subclipse.core.commands.UpdateResourcesCommand.run
(UpdateResourcesCommand.java:83)
        at
org.tigris.subversion.subclipse.ui.operations.UpdateOperation.execute(Up
dateOperation.java:73)
        at
org.tigris.subversion.subclipse.ui.operations.RepositoryProviderOperatio
n.execute(RepositoryProviderOperation.java:71)
        at
org.tigris.subversion.subclipse.ui.operations.SVNOperation.run(SVNOperat
ion.java:89)
        at
org.eclipse.team.internal.ui.actions.JobRunnableContext.run(JobRunnableC
ontext.java:144)
        at
org.eclipse.team.internal.ui.actions.JobRunnableContext$ResourceJob.runI
nWorkspace(JobRunnableContext.java:72)
        at
org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWor
kspaceJob.java:38)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

---------------------------------------------------------

I opened an issue, but when I looked at fixing it, the code already
did what I planned to change it to do. Also, when I tested this using
3.4 M7 I did not get a problem. Do you have any more ideas what might
be a contributing factor? Is it possible that these are also nested
projects? Meaning a project in your workspace is also a child folder
of another project?

-- 
Thanks
Mark Phippard
http://markphip.blogspot.com/
---------------------------------------------------------
I now tried also eclipse 3.4 M7 with SubClipse, Tag 1.3.15.
I have got the same troubles.
I tried a new Workspace with only 2 projects in the main workingset.
Project 1: util (svn: trunk/java/unstable/util)
Project 2: libs (svn: trunk/java/unstable/libs) (only a file project)
The 2 projects do not depend on each other.
Now i get the error when updating ie. Util
Workspace with other Projects:
Project 1: util (svn: trunk/java/unstable/util)
Project 2: libs (svn: branches/production/libs) (only a file project)
Now the update completes without an error
--> it seems that the problem occurs, when 2 projects are in the same
svn-tree
Additional info:
A.
Maybe this is a problem based on a problem we have found in eclipse 3.4:
When you import a project "production-appli" into eclipse, that has the
path "<some path>/appli"
then eclipse names this project only "appli" instead of
"production-appli" as named in the .project file.
B.
Until Subclipse Tag 1.3.11 the update had no problems with our projects
(i didnt try 1.3.12)
Thanks
Roland Gradenegger
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subclipse.tigris.org
For additional commands, e-mail: users-help_at_subclipse.tigris.org