lightweight checkout from svn in bzr-eclipse

[kilroo]

If you tell bzr_eclipse to create a new project from a lightweight checkout from a Subversion repository, I believe what happens is this:

bzr performs the requested task as expected. However, if I understand correctly a lightweight checkout of a subversion branch, as performed by bzr-svn, is effectively an svn checkout. It has the .svn directories instead of a .bzr directory and everything. I do use a shared repository, so it occurs to me that I am not completely sure whether there would be a .bzr directory if that were not the case, but I suspect there wouldn't be any difference.

Because of this, I suspect that bzr-eclipse will only be able to handle lightweight checkouts from subversion repositories if it is also fully capable of taking over, and using bzr to interact with, a normal svn checkout as well. As it stands, when the checkout is finished, bzr_eclipse pops up a small error window the title of which I cannot read, with no other visible information, and then logs the following error:

eclipse.buildId=I20091030-1201
java.version=1.6.0_14
java.vendor=Sun Microsystems Inc.
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US
Command-line arguments: -os win32 -ws win32 -arch x86 -clean

This is a continuation of log file C:\EclipseWorkspace\.metadata\.bak_1.log
Created Time: 2009-12-04 11:27:35.259

Error
Fri Dec 04 11:27:35 EST 2009

java.lang.NullPointerException
at org.vcs.bazaar.eclipse.internal.core.model.LocalBranch.getFile(LocalBranch.java:66)
at org.vcs.bazaar.eclipse.BzrWorkspaceRoot.getClient(BzrWorkspaceRoot.java:164)
at org.vcs.bazaar.eclipse.BzrWorkspaceRoot.getClient(BzrWorkspaceRoot.java:155)
at org.vcs.bazaar.eclipse.core.commands.BazaarCommand.getClient(BazaarCommand.java:85)
at org.vcs.bazaar.eclipse.core.commands.StatusCommand.run(StatusCommand.java:86)
at org.vcs.bazaar.eclipse.core.status.StatusUpdater.statusesToUpdate(StatusUpdater.java:49)
at org.vcs.bazaar.eclipse.core.status.StatusCacheManager.refreshStatus(StatusCacheManager.java:240)
at org.vcs.bazaar.eclipse.core.listeners.AbstractResourceChangeListener.refreshStatus(AbstractResourceChangeListener.java:66)
at org.vcs.bazaar.eclipse.core.listeners.AbstractResourceChangeListener.access$0(AbstractResourceChangeListener.java:64)
at org.vcs.bazaar.eclipse.core.listeners.AbstractResourceChangeListener$1.run(AbstractResourceChangeListener.java:34)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

The Team -> Share Project option on the resulting project is greyed out, which surprised me, because I thought I remembered that the first time I tried this the resulting project was not shared, but could be shared using Subclipse (supporting the idea that bzr-svn's lightweight checkout is identical to an svn checkout).

I don't know how practical it would be to support lightweight svn checkouts in bzr-eclipse, given what exactly bzr-svn seems to do with them, but unless that can be accomplished this should probably be noted as a limitation of bzr-eclipse.

[Guillermo Gonzalez (verterok)]

Hi,

Thanks for the detailed report.

if the bzr-svn lightweight co don't have a .bzr directory bzr-eclipse don't support it.

I'll try to figure out if there is something bzr-eclipse can do to behave correctly without breaking svn support (subclipse/subversive).

[Alexander Taler (alex-idereal)]

This could be related to #801882 does not load bzr plugins

[Piotr Piastucki (piastucki)]

Frankly speaking I do not quite see the benefits of using lightweight svn checkout compared to using svn directly.

[Piotr Piastucki (piastucki)]

I am closing the ticket as "Won't Fix" as due to technical issues we are going to deprecate lightweight checkouts in bzr-eclipse 1.3 and likely remove the support for lightweight checkouts completely in the future versions.