This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
I've got a repo with multiple (maven) projects, running into problems opening them: If I try to open the projects after checkout, one arbitrarily choosen tag directory is used for every project - not the most recent, neither trunk. With multiple projects, it is not a good idea to skip the topmost folder (which identifies the project, of course), but 'trunk' should be choosen for skipping (and opening the project). As a result, it's a pain to open a single project (You've to create the project folder manually, to make checkout possible), and it is impossible to open multiple projects.
I do not understand what you're trying to say. File -> Open Project does not open your project? I suggest you describe your repository and checkout folder structure, point to what's wrong and describe what you would expect. Thanks.
repo: proj1 | +- tags | | | +- 2.0 | | | | | +- src | | | +- 2.1 | | | | | +- src | | | +- 2.2 | | | | | +- src | | | +- 3.0 | | | +- src | +- trunk | +- src proj2 | +- tags | | | +- 1.0 | | | | | +- src | | | +- 1.2 | | | | | +- src | | | +- 2.5 | | | | | +- src | | | +- 4.0 | | | +- src | +- trunk | +- src When I try to open proj1 and proj2, project is created e.g. from proj1/tags/2.1 and proj2/tags/1.0 In both cases, project should be created from projx/trunk (eliminating 'trunk')
> When I try to open proj1 and proj2, project is created e.g. from proj1/tags/2.1 and proj2/tags/1.0 Where exactly? In the File -> New Project wizard? Isn't there a possibility to change the location of sources and nbproject metadata?
I see, we're talking about different things. Of course, it is always possible to create a project from sources - with or without VCS usage. But what's not possible is creating a project "on the fly" properly from a subversion checkout (though it's offered by the checkout dialog). BTW, there's a pom.xml, creating a maven project should thus work (and it does, but it's not properly working, as a subdirectory seems to be used arbitrarily for creating the project).
Is the repo public? Can i try myself?
No, sorry. It's an intranet source repository from my employer.
If i have the following repo setup: 224455 | +- tags | | | +- 1.0 | | | +- src | | | +- pom.xml +- trunk | +- src | +- pom.xml and i check out 224455 with "Scan for projects" selected in the Checkout dialog, i get the following dialog asking me to select projects to open (i can both see tags/1.0 and trunk versions and can easily select which project to open). Do you get anything else? Or does pom.xml reside in different folders?
Created attachment 129886 [details] open projects dialog
... and when i select the trunk version, it is indeed opened.
Hm, must admit it works now - must have done sth. wrong, probably I just hadn't noticed that the list of projects is initially unordered (and thus selected the last of a "package", i.e. the last one of a block with the same project name). However, IMHO, it would be helpful to show only trunk versions by default, or to make this behaviour selectable in dialog "Folders to Checkout" (instead or beneath the option "Skip <selected folder> ..."). If I do select the trunk version directly in the aforementioned dialog, the project directory isn't created correctly (as the name of the project will be "trunk"), and if I select the project's subversion root, I'll probably get hundreds of folders (if the project exists for several years and is very actively developed). Another (additional) option could be, to show only the latest (e.g. 10) tag/branch versions, to limit the list size.
well, the main problem with subversion is that we do not know for sure what version is trunk, branch or tag. For us they're simply folders. True, in some cases we could rely on a probable usual setup but that would not work always. Also, displaying just a subset of found projects is not a good idea, would be confusing for someone. The only reasonable thing that i could do is to somehow sort projects in the list.