Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 342170 - [poll] Option to enable tag/branch/merge from different repository locations
Summary: [poll] Option to enable tag/branch/merge from different repository locations
Status: CLOSED MOVED
Alias: None
Product: Subversive
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-07 10:26 EDT by Igor Vinnykov CLA
Modified: 2023-02-13 10:56 EST (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 Igor Vinnykov CLA 2011-04-07 10:26:10 EDT 
There is a request, that makes sense in some cases, but we would like to collect different opinions. Please vote +1 if you will be interested in this functionality.

Request:
There should be an option in the preferences where tag/branch/merge working sets with projects from different repository locations but with the same repository structre (trunk/tags/branches) can be allowed. 

Motivation:
We have a common set of plugins (for databinding, jpa, device control, ...) which are used in different projects. We always make a working set containing the project and a working set containing the plugins. Because the api of the common plugins can change over time, but projects are untouched (when bugfree
:) we need to be able to restore the last state for bugfixing or further development. Because team project sets just store the location of the plugin/project but not the revision, we need to tag them one by one.
Comment 1 Alexander Malic CLA 2011-04-07 10:34:02 EDT 
+1
Comment 2 Eclipse Webmaster CLA 2023-02-13 10:56:03 EST 
This issue has been migrated to https://gitlab.eclipse.org/eclipse/subversive/subversive/-/issues/82.