Home » Eclipse Projects » Eclipse Platform » CVS Versions problem
|
| Re: CVS Versions problem [message #49636 is a reply to message #48633] |
Tue, 27 May 2003 14:11   |
Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
The problem is that Eclipse needs to use a file to find out the tags of
a project (referred to as the auto-refresh file). By default, it uses
the .project file. You can configure Eclipse to use a different file by
selecting the project in the CVS Repositories view and choosing
Configure Branches and Versions.
Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
which causes the tags to be forgotten when the version category is
expanded for projects without a valid auto-refresh file. The workaround
is to select a valid auto-refresh file for that project.
Joss Wright wrote:
> I have a number of projects hosted at Sourceforge and previously created
> in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
> Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
> RELEASE_0_9_0 etc.
>
> However in Eclipse 2.1 when I browse the version tags for the same project
> no version tags are displayed, i.e. when I expand repository_location >
> Versions > my_project in the CVS Repositories view.
>
> I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
> this a bug or have I just not configured something new in Eclipse 2.1.
>
> I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
>
> Regards,
>
> Joss
>
>
>
>
|
|
|
| Re: CVS Versions problem [message #49939 is a reply to message #49636] |
Tue, 27 May 2003 15:08 |
 Joss Wright
Messages: 32
Registered: July 2009 |
Member |
|
|
Mchael,
Thanks for your prompt reply. One further question, what would be a valid
auto-refresh file for my project? It was only ever created by Eclipse 2.0
and the tags were created by Eclipse 2.0, when I select Configure Version
and tags for my repositry, the .vcm-meta file and .project file are both
listed in the configure tags window.
Thanks,
Joss
Michael Valenta wrote:
> The problem is that Eclipse needs to use a file to find out the tags of
> a project (referred to as the auto-refresh file). By default, it uses
> the .project file. You can configure Eclipse to use a different file by
> selecting the project in the CVS Repositories view and choosing
> Configure Branches and Versions.
> Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
> which causes the tags to be forgotten when the version category is
> expanded for projects without a valid auto-refresh file. The workaround
> is to select a valid auto-refresh file for that project.
> Joss Wright wrote:
> > I have a number of projects hosted at Sourceforge and previously created
> > in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
> > Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
> > RELEASE_0_9_0 etc.
> >
> > However in Eclipse 2.1 when I browse the version tags for the same project
> > no version tags are displayed, i.e. when I expand repository_location >
> > Versions > my_project in the CVS Repositories view.
> >
> > I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
> > this a bug or have I just not configured something new in Eclipse 2.1.
> >
> > I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
> >
> > Regards,
> >
> > Joss
> >
> >
> >
> >
|
|
|
| Re: CVS Versions problem [message #51683 is a reply to message #49939] |
Wed, 28 May 2003 13:04 |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
Does the .project file exist in the repository? Typically, projects
created with Eclipse and committed as is work fine in the CVS
repositories view. The only problems have occured for remote projects
that do not contain the .project file. In these cases, the auto-refresh
file can be changed to any file that does exist remotely (e.g.
..classpath if there is one).
Michael
Joss Wright wrote:
> Mchael,
>
> Thanks for your prompt reply. One further question, what would be a valid
> auto-refresh file for my project? It was only ever created by Eclipse 2.0
> and the tags were created by Eclipse 2.0, when I select Configure Version
> and tags for my repositry, the .vcm-meta file and .project file are both
> listed in the configure tags window.
>
> Thanks,
>
> Joss
>
>
> Michael Valenta wrote:
>
>
>>The problem is that Eclipse needs to use a file to find out the tags of
>>a project (referred to as the auto-refresh file). By default, it uses
>>the .project file. You can configure Eclipse to use a different file by
>>selecting the project in the CVS Repositories view and choosing
>>Configure Branches and Versions.
>>
>
>>Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
>>which causes the tags to be forgotten when the version category is
>>expanded for projects without a valid auto-refresh file. The workaround
>>is to select a valid auto-refresh file for that project.
>>
>
>>Joss Wright wrote:
>>
>
>>>I have a number of projects hosted at Sourceforge and previously created
>>>in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
>>>Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
>>>RELEASE_0_9_0 etc.
>>>
>>>However in Eclipse 2.1 when I browse the version tags for the same project
>>>no version tags are displayed, i.e. when I expand repository_location >
>>>Versions > my_project in the CVS Repositories view.
>>>
>>>I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
>>>this a bug or have I just not configured something new in Eclipse 2.1.
>>>
>>>I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
>>>
>>>Regards,
>>>
>>>Joss
>>>
>>>
>>>
>>>
>>>
>
>
>
>
|
|
|
| Re: CVS Versions problem [message #53503 is a reply to message #51683] |
Thu, 29 May 2003 09:24 |
Joss Wright
Messages: 32
Registered: July 2009 |
Member |
|
|
Michael,
All my projects have .project files in CVS, I have viewed the files
directly (using a web browser) and the .project file has been tagged with
a 3 tag versions, but these are not displayed by Eclipse 2.1.
Regards,
Joss
Michael Valenta wrote:
> Does the .project file exist in the repository? Typically, projects
> created with Eclipse and committed as is work fine in the CVS
> repositories view. The only problems have occured for remote projects
> that do not contain the .project file. In these cases, the auto-refresh
> file can be changed to any file that does exist remotely (e.g.
> ..classpath if there is one).
> Michael
> Joss Wright wrote:
> > Mchael,
> >
> > Thanks for your prompt reply. One further question, what would be a valid
> > auto-refresh file for my project? It was only ever created by Eclipse 2.0
> > and the tags were created by Eclipse 2.0, when I select Configure Version
> > and tags for my repositry, the .vcm-meta file and .project file are both
> > listed in the configure tags window.
> >
> > Thanks,
> >
> > Joss
> >
> >
> > Michael Valenta wrote:
> >
> >
> >>The problem is that Eclipse needs to use a file to find out the tags of
> >>a project (referred to as the auto-refresh file). By default, it uses
> >>the .project file. You can configure Eclipse to use a different file by
> >>selecting the project in the CVS Repositories view and choosing
> >>Configure Branches and Versions.
> >>
> >
> >>Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
> >>which causes the tags to be forgotten when the version category is
> >>expanded for projects without a valid auto-refresh file. The workaround
> >>is to select a valid auto-refresh file for that project.
> >>
> >
> >>Joss Wright wrote:
> >>
> >
> >>>I have a number of projects hosted at Sourceforge and previously created
> >>>in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
> >>>Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
> >>>RELEASE_0_9_0 etc.
> >>>
> >>>However in Eclipse 2.1 when I browse the version tags for the same project
> >>>no version tags are displayed, i.e. when I expand repository_location >
> >>>Versions > my_project in the CVS Repositories view.
> >>>
> >>>I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
> >>>this a bug or have I just not configured something new in Eclipse 2.1.
> >>>
> >>>I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
> >>>
> >>>Regards,
> >>>
> >>>Joss
> >>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
|
|
|
| Re: CVS Versions problem [message #53963 is a reply to message #53503] |
Thu, 29 May 2003 14:29 |
| Eclipse User |
|
|
|
Originally posted by: Michael_Valenta.oti.com
I've never seen this problem before. Is there anything in the log file?
To see what's happening under the hood, you could follow the directions
at the following URL:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/plat form-vcm-home/docs/online/cvs_features2.0/cvs-faq.html#misc_ 0
If you look at the output after you expand the empty version, you may
see a reason why it failed. If it loks like an Eclipse problem, open a
bug report and attach the output.
Michael
Joss Wright wrote:
> Michael,
>
> All my projects have .project files in CVS, I have viewed the files
> directly (using a web browser) and the .project file has been tagged with
> a 3 tag versions, but these are not displayed by Eclipse 2.1.
>
> Regards,
>
> Joss
>
> Michael Valenta wrote:
>
>
>>Does the .project file exist in the repository? Typically, projects
>>created with Eclipse and committed as is work fine in the CVS
>>repositories view. The only problems have occured for remote projects
>>that do not contain the .project file. In these cases, the auto-refresh
>>file can be changed to any file that does exist remotely (e.g.
>>..classpath if there is one).
>>
>
>>Michael
>>
>
>>Joss Wright wrote:
>>
>
>>>Mchael,
>>>
>>>Thanks for your prompt reply. One further question, what would be a valid
>>>auto-refresh file for my project? It was only ever created by Eclipse 2.0
>>>and the tags were created by Eclipse 2.0, when I select Configure Version
>>>and tags for my repositry, the .vcm-meta file and .project file are both
>>>listed in the configure tags window.
>>>
>>>Thanks,
>>>
>>>Joss
>>>
>>>
>>>Michael Valenta wrote:
>>>
>>>
>>>
>>>>The problem is that Eclipse needs to use a file to find out the tags of
>>>>a project (referred to as the auto-refresh file). By default, it uses
>>>>the .project file. You can configure Eclipse to use a different file by
>>>>selecting the project in the CVS Repositories view and choosing
>>>>Configure Branches and Versions.
>>>>
>>>>
>>>>Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
>>>>which causes the tags to be forgotten when the version category is
>>>>expanded for projects without a valid auto-refresh file. The workaround
>>>>is to select a valid auto-refresh file for that project.
>>>>
>>>>
>>>>Joss Wright wrote:
>>>>
>>>>
>>>>>I have a number of projects hosted at Sourceforge and previously created
>>>>>in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
>>>>>Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
>>>>>RELEASE_0_9_0 etc.
>>>>>
>>>>>However in Eclipse 2.1 when I browse the version tags for the same project
>>>>>no version tags are displayed, i.e. when I expand repository_location >
>>>>>Versions > my_project in the CVS Repositories view.
>>>>>
>>>>>I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
>>>>>this a bug or have I just not configured something new in Eclipse 2.1.
>>>>>
>>>>>I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
>>>>>
>>>>>Regards,
>>>>>
>>>>>Joss
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>
>
>
>
|
|
|
| Re: CVS Versions problem [message #56928 is a reply to message #53963] |
Fri, 30 May 2003 22:10 |
Joss Wright
Messages: 32
Registered: July 2009 |
Member |
|
|
Michael,
I have tested this issue with a new workspace and the version tags are
correctly displayed by the CVS Repository view. The project causing the
problem is in a workspace that was upgraded from an Eclipse 2.0 workspace,
this may be the cause of the problem.
I shall try and look at the CVS log file as suggested, I will also try
deleting and checking out a new version of the project from CVS to see if
this is a workaround.
Regards,
Joss
Michael Valenta wrote:
> I've never seen this problem before. Is there anything in the log file?
> To see what's happening under the hood, you could follow the directions
> at the following URL:
>
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/plat form-vcm-home/docs/online/cvs_features2.0/cvs-faq.html#misc_ 0
> If you look at the output after you expand the empty version, you may
> see a reason why it failed. If it loks like an Eclipse problem, open a
> bug report and attach the output.
> Michael
> Joss Wright wrote:
> > Michael,
> >
> > All my projects have .project files in CVS, I have viewed the files
> > directly (using a web browser) and the .project file has been tagged with
> > a 3 tag versions, but these are not displayed by Eclipse 2.1.
> >
> > Regards,
> >
> > Joss
> >
> > Michael Valenta wrote:
> >
> >
> >>Does the .project file exist in the repository? Typically, projects
> >>created with Eclipse and committed as is work fine in the CVS
> >>repositories view. The only problems have occured for remote projects
> >>that do not contain the .project file. In these cases, the auto-refresh
> >>file can be changed to any file that does exist remotely (e.g.
> >>..classpath if there is one).
> >>
> >
> >>Michael
> >>
> >
> >>Joss Wright wrote:
> >>
> >
> >>>Mchael,
> >>>
> >>>Thanks for your prompt reply. One further question, what would be a valid
> >>>auto-refresh file for my project? It was only ever created by Eclipse 2.0
> >>>and the tags were created by Eclipse 2.0, when I select Configure Version
> >>>and tags for my repositry, the .vcm-meta file and .project file are both
> >>>listed in the configure tags window.
> >>>
> >>>Thanks,
> >>>
> >>>Joss
> >>>
> >>>
> >>>Michael Valenta wrote:
> >>>
> >>>
> >>>
> >>>>The problem is that Eclipse needs to use a file to find out the tags of
> >>>>a project (referred to as the auto-refresh file). By default, it uses
> >>>>the .project file. You can configure Eclipse to use a different file by
> >>>>selecting the project in the CVS Repositories view and choosing
> >>>>Configure Branches and Versions.
> >>>>
> >>>>
> >>>>Also, there is a bug in 2.1 (which is fixed in 2.1.1 maintenance builds)
> >>>>which causes the tags to be forgotten when the version category is
> >>>>expanded for projects without a valid auto-refresh file. The workaround
> >>>>is to select a valid auto-refresh file for that project.
> >>>>
> >>>>
> >>>>Joss Wright wrote:
> >>>>
> >>>>
> >>>>>I have a number of projects hosted at Sourceforge and previously created
> >>>>>in Eclipse 2.0. In Eclipse 2.0 I can browse the Versions in the CVS
> >>>>>Repositories view and can see my version tags, e.g. RELEASE_2_0_0,
> >>>>>RELEASE_0_9_0 etc.
> >>>>>
> >>>>>However in Eclipse 2.1 when I browse the version tags for the same
project
> >>>>>no version tags are displayed, i.e. when I expand repository_location >
> >>>>>Versions > my_project in the CVS Repositories view.
> >>>>>
> >>>>>I have studied the Eclispe 2.1 CVS FAQ and searched the Eclipse site, is
> >>>>>this a bug or have I just not configured something new in Eclipse 2.1.
> >>>>>
> >>>>>I am using Windows 2000 with Eclipse version 2.1.0 build 200303272130.
> >>>>>
> >>>>>Regards,
> >>>>>
> >>>>>Joss
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
|
|
|
Goto Forum:
Current Time: Sat Jul 27 12:31:46 GMT 2024
Powered by FUDForum. Page generated in 0.04537 seconds |
] 
Search
Help
Register
Login
Home
