Should bzr-eclipse work correctly with --no-trees branches?
The layout I'm trying to use is that in one place on my local machine I have a shared treeless repository, which contains a trunk branch that is bound to a branch on another machine. I create feature branches from my local trunk. The project in my eclipse workspace contains a lightweight checkout which I switch among my local branches.
All of this works great, except that I have to do most of it from the command line.
Creating the checkout from within Eclipse isn't possible because when I select the branch directory the "next" option is still greyed out, but if I checkout from the command line I can import the directory as a project and share it with bzr with no problem.
From the Team menu, update seems to work fine, but switch is greyed out and commit always says there is nothing to commit. From the command line those operations work fine (and bzr xmlstatus seems to have appropriate output when run from the command line).
Revert also reports no changes to revert, but reverting the whole branch works.
I'm just wondering if all this is known/expected behavior, or if I should try to pull together a more detailed report and file a bug (whether here or with javierder).
I'm using Eclipse Helios (3.6) milestone 5, javierder's unofficial bzr-eclipse 1.1.1.211 (which I suppose might be the problem), and bzr 2.1.0 on Windows XP.
Question information
- Language:
- English Edit question
- Status:
- Answered
- Assignee:
- No assignee Edit question
- Last query:
- Last reply:
Can you help with this problem?
Provide an answer of your own, or ask kilroo for more information if necessary.