Bug 304493 - [Sync View][Apply Patch] Apply Patch in Synchronize view should not be blocked by ongoing synchronization
Summary: [Sync View][Apply Patch] Apply Patch in Synchronize view should not be blocke...
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Team (show other bugs)
Version: 3.6   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: polish
Depends on:
Blocks:
 
Reported: 2010-03-03 06:36 EST by Markus Keller CLA
Modified: 2019-09-02 14:55 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2010-03-03 06:36:16 EST
I20100302-0800

Apply Patch in Synchronize view should not be blocked by ongoing synchronization. 

I started a Synchronize with CVS operation on my whole workspace, and when I then apply a patch into the Synchronize view, nothing happens.

The progress view shows a "Synchronize Patch" job with zero progress. When I manually switch to the "Patch" synchronization, I get an empty page with links to Populate or Synchronize. When I click Populate, the Sync view correctly shows the patch contents.
Comment 1 Markus Keller CLA 2010-04-27 04:35:36 EDT
Ping. 'Populate' should be clicked automatically.
Comment 2 Markus Keller CLA 2010-05-06 11:23:33 EDT
I run into this bug quite often. It's especially confusing when I paste the patch to Package Explorer and have "Apply Patch in Synchronize view" enabled, since I get no feedback at all.

Would make a good RC1 polish item.
Comment 3 Markus Keller CLA 2010-06-04 07:20:48 EDT
For 3.7, please?
Comment 4 Tomasz Zarna CLA 2010-06-07 03:31:32 EDT
Added to Workspace 3.7 Development Plan draft[1]. Feel free to add there other bugs that you think have to be fixed in 3.7.

[1] http://wiki.eclipse.org/Workspace3.7
Comment 5 Eclipse Genie CLA 2018-10-19 13:48:52 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.

--
The automated Eclipse Genie.
Comment 6 Lars Vogel CLA 2019-09-02 14:55:00 EDT
This bug has been marked as stalebug a while ago without any further interaction.

If this report is still relevant for the current release, please reopen and remove the stalebug whiteboard flag.