.jupiter file is rearranged when creating a new review, which complicates merging

[GoogleCodeExporter]

I find that when working with a team, we have to be very careful when
checking in our .jupiter file because it appears that when a new review is
added, it doesn't just insert the new review element, it actually seems to
rearrange the existing review elements, and perhaps modifies the entire
file.  This makes it very difficult to merge with subversion or any other
SCM system.

It really would be more robust if the .jupiter file had basic defaults, but
any reviews that are created by the team go into separate files, like as
the review comments themselves (I'm not suggesting the review data itself
goes into the comments file).

Original issue reported on code.google.com by davidmic...@gmail.com on 5 Mar 2010 at 9:26

[GoogleCodeExporter]

Just to add more information to this, this problem is the biggest annoyance I 
have
with this plugin.  In general, the plugin is a big help, but whenever two 
people are
making changes to this file at the same time it creates a big mess.

This would have worked better if "<reviewnname>.review" files were first-class
components that get edited in the Editor view.  Each ".review" file describes a
single review (not issues), and its contents are initialized from defaults set 
in the
".jupiter" file.

Issues would go into a "<reviewname>-<user>.issues" file.

Original comment by davidmic...@gmail.com on 7 Apr 2010 at 6:12