Merge lp:~wallyworld/bzr4j/track-submit-changes into lp:bzr4j
Status: | Needs review |
---|---|
Proposed branch: | lp:~wallyworld/bzr4j/track-submit-changes |
Merge into: | lp:bzr4j |
Prerequisite: | lp:~frankoid/bzr4j/idea11-fixes |
Diff against target: |
476 lines (+181/-52) 9 files modified
modules/core/src/main/java/org/emergent/bzr4j/core/cli/BzrAbstractExec.java (+1/-1) modules/core/src/main/java/org/emergent/bzr4j/core/cli/CmdContext.java (+1/-1) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/BzrProjectSettings.java (+27/-0) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/command/BzrMiscCommand.java (+12/-0) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/provider/BzrChangeProvider.java (+11/-1) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/ui/BzrConfigurationProjectPanel.form (+47/-5) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/ui/BzrConfigurationProjectPanel.java (+62/-15) modules/intellij/src/main/java/org/emergent/bzr4j/intellij/ui/BzrSwitchDialog.java (+19/-29) modules/intellij/src/main/resources/org/emergent/bzr4j/intellij/BzrVcsMessages.properties (+1/-0) |
To merge this branch: | bzr merge lp:~wallyworld/bzr4j/track-submit-changes |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Patrick Woodworth | Pending | ||
Review via email: mp+88797@code.launchpad.net |
This proposal supersedes a proposal from 2010-10-06.
Description of the change
Enhancement proposal
When tracking changes to my projects, via the Changes tab or the gutter change indicators, I often want to see what the differences are against the submit or ancestor revision, not just the branch tip revision. This allows me to easily see what a merge proposal diff would look like and makes it much easier to track the overall changes for the entire time working on the branch, not just since the last commit. At the moment, as soon as you do a local commit, all the changes are reset and you lose sight of the difference between your work and the trunk. Currently, you can run bzr from the command line for get a text based diff but it's much more convenient to have it all integrated into the IDE.
Implementation
Add new options "Track Changes Against Local|Submit|
You can go to the plugin config screen and change the setting, and then you just need to hit refresh on the Changes tab for the chosen tracking method to be used. So it's easy enough to alter the method used as the need arises from within the IDE.
I had to add the use of the "-q" flag to the bzr command invocation since otherwise bzr sadly prints some info text to stderr and this confuses the command error detection.
The bulk of the changes in the diff (BzrConfigurati
Unmerged revisions
- 61. By Ian Booth
-
Merge in latest trunk and add support for tracking against ancestor branches
- 60. By Francis Devereux
-
Update <change-notes> in plugin.xml and bump version to 2.6.2-SNAPSHOT
- 59. By Francis Devereux
-
Add methods to BzrAnnotation to fix compilation against IntelliJ IDEA 11.0
- 58. By Francis Devereux
-
Add Set<String> feedback argument to BzrCheckinEnvir
onment. commit so that it compiles against IntelliJ IDEA 11.0 - 57. By Francis Devereux
-
Form changes made automatically when building with IntelliJ 11.0
- 56. By Francis Devereux
-
Update BzrFileRevision to compile against IntelliJ IDEA 11.0 SDK and to use ContentRevision
Cache - 55. By Francis Devereux
-
VcsUtil.
showErrorMessag e has moved to VcsImplUtil - 54. By Francis Devereux
-
Fixed IDEA 10 (latest git as of 14 Feb 2011) compile errors
I could also add an option to track changes against ancestor: as well as submit: if that seems appropriate. I guess there's also work that could be done to add these sorts of options to the right click bzr menu eg "Compare With Submit Revision" etc. I'll look into that if this mp gets approved.