Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 318909 - Attaching context to task changes description in CollabNet SourceForge
Summary: Attaching context to task changes description in CollabNet SourceForge
Status: RESOLVED NOT_ECLIPSE
Alias: None
Product: z_Archived
Classification: Eclipse Foundation
Component: Mylyn (show other bugs)
Version: 3.4   Edit
Hardware: Other Linux
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Mark Phippard CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-05 11:27 EDT by James Missing name CLA
Modified: 2010-07-06 01:48 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description James Missing name CLA 2010-07-05 11:27:06 EDT 
I am using Mylyn to attatch context to tasks from a Collabnet SourceForge repository, but whenever I attach a context for the first time it always says "Description change from" but the actual content doesn't change. I think it may be related to it adding different newlines (e.g. \n vs \r\n) or possibly adding a newline at the end of the description.

We are using CollabNet SourceForge 5.0.0.0.298 (the repo server), and I am using Eclipse Helios 3.6 (build ID 20100617-1415) and CollabNet Desktop 2.0.5 on an Ubuntu 10.04 32-bit system

An example of what I see in SourceForge after uploading context would be:

mylyn-context.zip (2.45 KB)

Update
Added an attachment.
Description changed from
Task description goes here
to
Task description goes here

-- Configuration Details --
Product: Eclipse 1.3.0.20100617-0520 (org.eclipse.epp.package.php.product)
Installed Features:
 org.eclipse.mylyn_feature 3.4.0.v20100608-0100-e3x
Comment 1 Steffen Pingel CLA 2010-07-05 13:17:04 EDT 
That sounds like a problem specific to the CollabNet Desktop integration. Mark, can you take this on?
Comment 2 Mark Phippard CLA 2010-07-05 13:59:04 EDT 
This is a known issue in the TeamForge SOAP API.  It was fixed in TeamForge 5.2 Patch 1.  Upgrade your TeamForge server to the latest version -5.3 patch 2
Comment 3 Steffen Pingel CLA 2010-07-06 01:48:36 EDT 
Thanks! I'll mark this bug as resolved then.