search

jsakuda / jupiter-eclipse-plugin

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

.jupiter file being overwritten #69

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. User 1 commits a new review ID in cvs (e.g. v1.541)
2. User 2 updates the .jupiter file (right click on .jupiter >> Team >>
Update). Version is now 1.541
3. User 2 creates a new review ID
4. User 2 commits the file in cvs. If there is a "not synch" error. Just
refresh the file then the file will commit.

What is the expected output? What do you see instead?
After User 2 commits the new review ID he created, the review ID created by
User 1 should not be overwritten. Currently, this can be avoided by doing a
"refresh/F5" between steps #2 and #3. I have tested the latest release
(jupiter 3.4.2), and still found the behavior was still present. Can you
suggest any convenient work-around for this at the moment?

What version of the product are you using? On what operating system?
jupiter 3.4.0/jupiter 3.4.2
eclipse 3.3.1.1
jdk1.6.0_10

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 3.3.1.1

Please provide any additional information below.

Original issue reported on code.google.com by hoosedye...@gmail.com on 24 Apr 2009 at 8:20

GoogleCodeExporter commented 8 years ago 
by the way, i am using windows xp. thanks.

Original comment by hoosedye...@gmail.com on 24 Apr 2009 at 8:22

GoogleCodeExporter commented 8 years ago 
it seems that the problem is that Jupiter is using the old version (the version
before the update on step2), and adds the review ID in step 3 to that old 
version.
this is probably why the changes done by User 1 is lost after step 4.

Original comment by hoosedye...@gmail.com on 24 Apr 2009 at 8:33

GoogleCodeExporter commented 8 years ago 
This is mostly likely related to the fact that Eclipse doesn't refresh the 
workspace
automatically by default.  Although, if you are using the CVS capabilities 
inside of
Eclipse I would think it would have refreshed the file for you because it knows 
it
modified the file by updating it from version control.  Normally old versions of
files end up getting used if the file is somehow modified outside of Eclipse and
automatic refresh is turned off.

As of now, Jupiter forces a file refresh after it modifies the file so it 
should show
as modified in the Package Explorer.  It does not however refresh it beforehand
because it was assumed that the file in the workspace is up to date.  I can 
force a
refresh beforehand to work around the fact the workspace doesn't automatically 
update
if people prefer this.

Original comment by jsakuda on 24 Apr 2009 at 7:01

GoogleCodeExporter commented 8 years ago 
Yes, it seems so. Will the fix be available in the next release? May I know 
when we
can expect the next release? Thanks.

Original comment by hoosedye...@gmail.com on 25 Apr 2009 at 1:45

GoogleCodeExporter commented 8 years ago 
Yes I can put it in the next release.  But the next release I was planning was
Jupiter 3.5 which would come after Eclipse 3.5 is released.  According to this:
http://www.eclipse.org/eclipse/development/freeze_plan_3.5.php Eclipse 3.5 
won't be
out until June.

Original comment by jsakuda on 25 Apr 2009 at 2:21

GoogleCodeExporter commented 8 years ago

Original comment by jsakuda on 25 Apr 2009 at 2:21

GoogleCodeExporter commented 8 years ago

Original comment by jsakuda on 25 May 2009 at 3:45

GoogleCodeExporter commented 8 years ago 
Marking as part of release 3.5.0.

Original comment by jsakuda on 25 May 2009 at 3:45