I updated to 1.4.3 today and it appears to have fixed this problem for me.
(and I also appreciate the reversion of functionality in the commit dialog)
Thanks,
- David
Mark Phippard wrote:
>On Thu, Jul 17, 2008 at 3:06 PM, Levi Purvis <subclipse_at_purvis.ws> wrote:
>
>>On Sun, Jun 29, 2008 at 6:24 PM, Mark Phippard <markphip_at_gmail.com> wrote:
>>
>>>On Fri, Jun 27, 2008 at 9:46 AM, Joe <qbproger_at_gmail.com> wrote:
>>>
>>>>The second problem:
>>>>
>>>>When I do an update on the project folder I get the following error:
>>>>
>>>>An internal error occurred during: "SVN Update".
>>>>Attempted to beginRule: P/(removed), does not match outer scope rule:
>>>>P/(removed)
>>>>
>>>>If the actual part after the P/ is useful I'd rather send it to an
>>>>individual person than the whole mailing list. If I do an update on
>>>>the src folder inside the project it works fine.
>>>>
>>>You are not the only person to report this. We have not been able to
>>>recreate it to fix it. If you have any ideas on the secret recipe to
>>>reproduce let us know. When we see this kind of error, there is one
>>>semi-obvious fix we can make. When we looked at code, that fix was
>>>already in it. So we are at a loss as to what to do at the moment.
>>>
>>I am having the exact same problem. I have about 40 projects in my
>>workspace that were imported from an existing directory tree (the
>>projects all share a revisioned 'trunk' folder). The directory tree
>>was checked out from the 'trunk' root separately from Eclipse.
>>
>>The projects were imported using File -> Import -> Existing Projects
>>into Workspace
>>
>>The projects were *not* copied into my workspace.
>>
>>I'm on Windows XP; Eclipse 3.4; Subclipse 1.4.1
>>
>>Has there been an issue filed for this, yet? Any other info that I can provide?
>>
>
>We committed a fix this week for the one scenario we were presented
>that we could duplicate.
>
>It involved nested projects. Where your workspace contained the following:
>
>/MasterProject
> /Project
> /Project.foo
>/Project
>/Project.foo
>
>So the MasterProject was in your workspace, plus the additional nested
>projects were also in workspace. Additionally, it seemed to only
>happen when one project's name was a subset of another project's name.
>
>When this problem was first reported, the user said they were not
>using nested projects. We specifically asked that.
>
>Subversion 1.5.1 is coming out next Friday and we will do a new
>Subclipse release after that.
>
Received on 2008-08-12 05:27:33 CEST