Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 146322

Summary:	[Modules] CVS plug-in doesn't allow options for module check-out
Product:	[Eclipse Project] Platform	Reporter:	Jeff Johnston <jjohnstn>
Component:	CVS	Assignee:	platform-cvs-inbox <platform-cvs-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	jjohnstn, tomasz.zarna
Version:	3.3	Keywords:	helpwanted
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Jeff Johnston

2006-06-09 15:09:40 EDT

Sourceware.org has a number of Open Source projects including newlib.  The server is sources.redhat.com and the repository is /cvs/src

To check out newlib, one simply uses the module-name: newlib.  This module contains among other things, the subdirectory src/newlib.

When asked to specify a module name under: Import -> CVS -> Projects from CVS -> pick server -> Select Module

If newlib is specified for "Use specified module name", it only gets the newlib subdirectory and doesn't check out this out as src/newlib.

If "Use existing module" is used and the newlib module vs the newlib directory is clicked, it can indeed find the newlib module vs the newlib directory, however, the "Check Out As" page is not offered so the project cannot be checked out as a Std Make C Project, for example.

Either the "Check Out As" page should be enabled for the check-out existing module or modules should take precendence on the "Use specified module name".

Comment 1 Jeff Johnston

2007-02-28 16:05:53 EST

I have updated the summary of this bug as the current behavior has changed since the bug was originally opened, but it is still not what is desired.  Thus, let me clarify.

What occurs is that checking out a CVS module (in this case :pserver:sources.redhat.com:/cvs/src module(newlib)) does not allow at the time of check-out:

  a) naming of the project
  b) running a wizard for the project

Both a and b have to be done "after-the-checkout" using 1) a refactor of the project name and 2) a project converter, so it seems as if it would be straightforward to implement this feature.  Is there some explanation why this currently is prohibited for modules but enabled for directories?

Comment 2 Tomasz Zarna

2008-04-10 11:24:52 EDT

It looks like a dupe of bug 66884 to me Jeff, don't you think?

Comment 3 Jeff Johnston

2008-04-10 13:18:07 EDT

(In reply to comment #2)
> It looks like a dupe of bug 66884 to me Jeff, don't you think?
> 

So, because newlib is a defined module name in CVSROOT/modules, you are saying you don't know if that might represent multiple projects (i.e. top-level directories)?  Doesn't everything in the CVSROOT/modules file have to fall under the top-level source directory (in this case src) and thus there is one project?  When I check it out, I indeed get one project called "src" with multiple sub-directories.

What is a scenario where one project under the top source directory doesn't hold true?  What would I have to do in our repository to make it so you would know what is actually occurring?

Comment 4 Eclipse Webmaster

2019-09-06 15:32:58 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.

Comment 5 Eclipse Genie

2021-09-13 18:40:20 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. As such, we're closing this bug.

If you have further information on the current state of the bug, please add it and reopen this bug. 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.