search

wuranjia / jupiter-eclipse-plugin

Automatically exported from code.google.com/p/jupiter-eclipse-plugin
1 stars 6 forks source link

Not Able to Continue a Previous Session #43

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Start a Jupiter review session and stop before completing
2. Close Eclipse and shutdown computer
3. Attempt to restart the Jupiter review session (e.g., the next day)

What is the expected output? What do you see instead?

I expect the previous Jupiter review file to be shown and have the ability
to add more issues to the current review file.  However, the new session
creates a new review file, deleting the previous file as soon as a new
issue is documented.

What version of the product are you using? On what operating system?

Jupiter 3.4.0 on Windows XP SP2 

If applicable, what editor does the problem occur in (Jupiter is tested
against the 'Eclipse for RCP/Plug-in Developers' so the editors may vary)?

Eclipse Classic

from About:

Eclipse Platform

Version: 3.4.0.v20080610-9I96EhtEm-T_5LxIsybz-3MdGZmOA3uwv7Ka_M
Build id: I20080617-2000

Please provide any additional information below.

We are using Visual Source Safe 6.0 as version control

I attempted to save the review file and restart, and also without having
the review file in VSS; both with the same result.

Should you need more info please contact me.

Original issue reported on code.google.com by Michael....@tcomlp.com on 10 Sep 2008 at 5:45

GoogleCodeExporter commented 9 years ago 
I have found a NullPointerException being thrown and I think that may be 
causing this
issue.  I will push a minor release with this fix as I think it is a bad bug.  
Thanks
for the detailed information.

Original comment by jsakuda on 10 Sep 2008 at 6:19

GoogleCodeExporter commented 9 years ago

Original comment by jsakuda on 19 Oct 2008 at 9:36

GoogleCodeExporter commented 9 years ago 
I do believe that this is fixed in the latest changes that were committed.  
Please let me know if this problem 
persists in Jupiter 3.4.1.  If it does, I will reopen this issue and reassign 
it to the 3.4.2.

Original comment by jsakuda on 27 Oct 2008 at 9:49