Bug 225323 - When create a new Branch, old version is tagged for some files
Summary: When create a new Branch, old version is tagged for some files
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: CVS (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform Team Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-04-02 09:03 EDT by Evguenia CLA
Modified: 2019-09-06 16:04 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Evguenia CLA 2008-04-02 09:03:23 EDT
Hello,

We created a branch in a project
There are errors in creating tags for two files of the project
- web.xml and
- .classpath

For these files intermediate versions where tagged, and not the last ones.

For example we are at the version 1.22 of the web.xml.
New branche( BRANCH1) was created and the tag (Root_BRANCH1) was added to the version 1.17 of web.xml.

Thanks a lot for your help!
Comment 1 Walter Harley CLA 2008-04-02 11:00:07 EDT
This has nothing whatsoever to do with JDT APT as far as I can tell.  Reclassifying to Platform.
Comment 2 Tomasz Zarna CLA 2008-04-03 05:53:13 EDT
Evguenia, what version of Eclipse are you using? Is it 3.2? Are you able to reproduce it using a more up-to-date build?
Comment 3 Evguenia CLA 2008-04-03 06:18:50 EDT
Tomasz, we've used 3.2 version.
I've never seen the same problem with 3.3
Sorry, i can't retest it actually (in this project tag number on CVS is critical)

It's not so important, we'd just like to know WHY it's happened?
For which reasons do you think is it possible to have such behaviour? 

Before creating a branch on CVS, must I totally synchronize the project?
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:04:55 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.