stale name used after renaming project

Bug #204174 reported by RLVJ
4
Affects Status Importance Assigned to Milestone
Bazaar Plugin for Eclipse
Fix Released
High
Guillermo Gonzalez

Bug Description

After renaming a project, BzrEclipse continues to use the former, now incorrect, name of the project in operations.

Software Versions:
BzrEclipse 0.0.17
Bazaar 1.2.0

Revision history for this message
RLVJ (nathan-johnson) wrote :
Changed in bzr-eclipse:
importance: Undecided → High
status: New → Confirmed
Changed in bzr-eclipse:
assignee: nobody → guillo.gonzo
status: Confirmed → In Progress
Revision history for this message
Russel Winder (russel) wrote :
Download full text (5.0 KiB)

There is also a severe problem if the whole repository gets moved -- I guess it is the same metadata held by the Bazaar plugin.

The question is why does the plugin cache the information at all?

This is Eclipse 3.3.2 M20080221-1800, Bazaar 1.1, BazaarClient 0.0.9.200712280044.

org.vcs.bazaar.eclipse.internal.core.BazaarException: A unexpected error ocurred
        at org.vcs.bazaar.eclipse.internal.core.BazaarException.wrapException(BazaarException.java:119)
        at org.vcs.bazaar.eclipse.core.commands.StatusCommand.run(StatusCommand.java:92)
        at org.vcs.bazaar.eclipse.core.status.StatusUpdater.statusesToUpdate(StatusUpdater.java:54)
        at org.vcs.bazaar.eclipse.core.status.StatusCacheManager.refreshStatus(StatusCacheManager.java:215)
        at org.vcs.bazaar.eclipse.core.listeners.FileModificationManager.refreshStatusInfitite(FileModificationManager.java:165)
        at org.vcs.bazaar.eclipse.core.listeners.FileModificationManager.access$1(FileModificationManager.java:161)
        at org.vcs.bazaar.eclipse.core.listeners.FileModificationManager$2.runInWorkspace(FileModificationManager.java:135)
        at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
        at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: org.vcs.bazaar.client.commandline.CommandLineException: Cannot run program "/usr/bin/bzr" (in directory "/home/users/russel/workspace_3.3/Gant_1.1.X_Bazaar"): java.io.IOException: error=2, No such file or directory
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
        at org.vcs.bazaar.client.commandline.internal.ShellCommand.runCommand(ShellCommand.java:52)
        at org.vcs.bazaar.client.commandline.internal.Command.execute(Command.java:77)
        at org.vcs.bazaar.client.commandline.commands.MultiFileCommand.execute(MultiFileCommand.java:36)
        at org.vcs.bazaar.client.commandline.CommandLineClient.run(CommandLineClient.java:566)
        at org.vcs.bazaar.client.commandline.CommandLineClient.status(CommandLineClient.java:388)
        at org.vcs.bazaar.eclipse.core.commands.StatusCommand.executeAndFilterLogOutput(StatusCommand.java:131)
        at org.vcs.bazaar.eclipse.core.commands.StatusCommand.run(StatusCommand.java:77)
        ... 7 more
Caused by: java.io.IOException: Cannot run program "/usr/bin/bzr" (in directory "/home/users/russel/workspace_3.3/Gant_1.1.X_Bazaar"): java.io.IOException: error=2, No such file or directory
        ... 15 more
Caused by: java.io.IOException: java.io.IOException: error=2, No such file or directory
        at java.lang.UNIXProcess.<init>(UNIXProcess.java:148)
        at java.lang.ProcessImpl.start(ProcessImpl.java:65)
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:452)
        ... 14 more
org.vcs.bazaar.eclipse.internal.core.BazaarException[-6]: org.vcs.bazaar.client.commandline.CommandLineException: Cannot run program "/usr/bin/bzr" (in directory "/home/users/russel/workspace_3.3/Gant_1.1.X_Bazaar"): java.io.IOException: error=2, No such file or directory
        at java.lang.ProcessBuilder.start(ProcessBuilder.java:459)
        at org.vcs.bazaar.client.commandline.interna...

Read more...

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Russel,
   The quick answer is that there's no need to cache that information.
   I'm working on this (actually I almost finished the fix), stay tuned ;-)

Cheers,

Revision history for this message
Russel Winder (russel) wrote :

It did seem to me that there should be no need to cache this information, particularly in a way that cannot be updated as needed, so it is good to hear that this mis-feature is going away.

I rarely use Eclipse myself, so this is not a big deal for me. However I seem to be in a minority these days, most people use Eclipse, NetBeans or IntelliJ-IDEA for development, so I always demonstrate with Eclipse -- and also NetBeans where possible but they support Mercurial not Bazaar.

Thanks.

Changed in bzr-eclipse:
status: In Progress → Fix Committed
Changed in bzr-eclipse:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.