Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 81960 - [FAQ] [Change Sets] Change sets don't work in Incomming mode using extssh
Summary: [FAQ] [Change Sets] Change sets don't work in Incomming mode using extssh
Status: VERIFIED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows 2000
: P3 normal with 1 vote (vote)
Target Milestone: 3.1 M7   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-12-28 06:19 EST by Roel Spilker CLA
Modified: 2005-09-28 15:57 EDT (History)
2 users (show)

See Also:


Attachments
Screenshot showing the "show change set" button (12.18 KB, image/png)
2005-01-04 05:13 EST, Sylvain Pasche CLA
no flags Details
Log of Eclipse Synchronize on pserver (3.60 KB, text/plain)
2005-01-10 09:37 EST, Roel Spilker CLA
no flags Details
Log of Eclipse Synchronize on extssh (8.14 KB, text/plain)
2005-01-10 09:38 EST, Roel Spilker CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Roel Spilker CLA 2004-12-28 06:19:45 EST
Using extssh to connect to the repository, all incomming changes are collected 
under "Unassigned Remote Changes". When I use pserver, all works fine.
Comment 1 Sylvain Pasche CLA 2004-12-29 05:30:55 EST
Hello,
I have this problem with both extssh and pserver modes. I am using 3.1M4 under
linux/gtk.
Comment 2 Roel Spilker CLA 2005-01-04 04:38:56 EST
Sylvain,

A collegue of mine suggest that under linux/gtk the button "Show Change Sets", 
in the synchonize view toolbar, is by default not visible. This button can be 
shown by resizing the synchronize view. When you use pserver, pushing this 
button results in grouping the incomming changes by Change Set.

Roel
Comment 3 Sylvain Pasche CLA 2005-01-04 05:12:09 EST
Hi,

This button is visible even on linux/gtk. (However, is is enabled only in
incoming mode [new feature since 3.1M2]).

You can see on the attached screenshot.

Cheers,
Sylvain
Comment 4 Sylvain Pasche CLA 2005-01-04 05:13:27 EST
Created attachment 16906 [details]
Screenshot showing the "show change set" button
Comment 5 Jean-Michel Lemieux CLA 2005-01-05 16:12:11 EST
What CVS server version are you using. The grouped change sets is based on being
able to parse the logs.
Comment 6 Roel Spilker CLA 2005-01-05 19:17:27 EST
Concurrent Versions System (CVS) 1.11.5 (client/server)
Comment 7 Sylvain Pasche CLA 2005-01-06 03:33:05 EST
using version 1.11.1 (debian woody).

I wanted to test version 1.12.9 on my local machine through pserver, but I got
an exception when I did the update:

Error 2005-01-06 09:25:02.217 An internal error occurred during: "Synchronize
View: Processing label changes".
java.lang.NullPointerException
at java.util.Calendar.setTime(Calendar.java:1032)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:785)
at java.text.SimpleDateFormat.format(SimpleDateFormat.java:778)
at java.text.DateFormat.format(DateFormat.java:314)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector$CVSCheckedInChangeSet.<init>(CVSChangeSetCollector.java:109)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.createChangeSetFor(CVSChangeSetCollector.java:368)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addRemoteChange(CVSChangeSetCollector.java:338)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addSingleRevision(CVSChangeSetCollector.java:285)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addSyncInfoToCommentNode(CVSChangeSetCollector.java:252)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.addLogEntries(CVSChangeSetCollector.java:230)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector.access$0(CVSChangeSetCollector.java:225)
at
org.eclipse.team.internal.ccvs.ui.subscriber.CVSChangeSetCollector$2.run(CVSChangeSetCollector.java:216)
at
org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler$8.run(SynchronizeModelUpdateHandler.java:659)
at
org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler$RunnableEvent.run(SynchronizeModelUpdateHandler.java:125)
at
org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler.executeRunnable(SynchronizeModelUpdateHandler.java:705)
at
org.eclipse.team.internal.ui.synchronize.SynchronizeModelUpdateHandler.processEvent(SynchronizeModelUpdateHandler.java:218)
at
org.eclipse.team.internal.core.BackgroundEventHandler.processEvents(BackgroundEventHandler.java:310)
at
org.eclipse.team.internal.core.BackgroundEventHandler$1.run(BackgroundEventHandler.java:154)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:66)
Comment 8 Michael Valenta CLA 2005-01-07 13:32:57 EST
Roel, could you follow the steps in this URL to get a trace of the 
communications between the server and client.

http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/platform-vcm-
home/docs/online/cvs_features2.0/cvs-faq.html#misc_0

This will should us what the rlog command is getting from the server. Ideally, 
if you could do it for both extssh and pserver, we could more easily pinpoint 
the difference.

P.S. I'm moving this to the REMIND bucket to await your respone.
Comment 9 Roel Spilker CLA 2005-01-10 09:35:44 EST
Trace logs for both pserver and extssh created.
Comment 10 Roel Spilker CLA 2005-01-10 09:37:40 EST
Created attachment 17028 [details]
Log of Eclipse Synchronize on pserver

As requested
Comment 11 Roel Spilker CLA 2005-01-10 09:38:07 EST
Created attachment 17029 [details]
Log of Eclipse Synchronize on extssh

As requested
Comment 12 Michael Valenta CLA 2005-01-10 11:03:42 EST
The problem is that your two repositories are different versions. The rlog 
command is using an option (-S) trhat is supported in 1.11.5 (your pserver 
repository) but not is 1.11.1p1 (your extssh repository). If you want to use 
change logs with your extssh repository, you will need to upgrade it. YOu 
probably should anyway since there have been important security fixes made in 
the latest 1.11 releases.
Comment 13 Sylvain Pasche CLA 2005-01-10 11:42:06 EST
Does it make sense let the client have knowledge of the remote cvs version, and
adapt its parameter accordingly ?

Actually, I have to work with some remote cvs servers, and I don't have the
ability to tell the admin to update them. I think this problem could happen to
other people too.

Or why not have a check on the cvs remote version (maybe at startup), and warn
the user that he should update its version, to prevent problems (and to avoid
people filling bugzilla with duplicates of this bug) ?
Comment 14 Michael Valenta CLA 2005-01-10 14:00:54 EST
What you suggest makes sense bot involves a fair amount of work. We do not 
have the manpower to do this (unless you want to provide a patch;-).
Comment 15 Roel Spilker CLA 2005-01-13 04:46:00 EST
Upgrading from 1.11.1p1 to 1.11.5 worked. Thank you for your suggestion. 

The reason we still used 1.11.1p1 is that that is the version provided with  
Debian stable.
Comment 16 Michael Valenta CLA 2005-04-20 14:21:23 EDT
I've added the entry to the FAQ
Comment 17 Michael Valenta CLA 2005-05-10 11:11:58 EDT
Verified