Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test projects are being imported when using the "official" Oomph installation #903

Closed
fedejeanne opened this issue Nov 3, 2023 · 3 comments

Comments

@fedejeanne
Copy link
Contributor

See #902 (comment)

When using this installer, some Test projects are being added to the WS (see this other comment)

@merks fyi

@merks
Copy link
Contributor

merks commented Nov 4, 2023

The assertion of the issue title does not appear to be true. In my SDK workspace, which includes the JDT setup, you can see that the source locator property is set to not consider nested projects and a manual "import projects" on the clone shows that a bunch of nested projects are not yet imported into the workspace.

image

So I don't think it is the Oomph setup that did the importing of those projects.

@fedejeanne
Copy link
Contributor Author

I tested again in Windows and the configuration seems fine: the folders are checked out from GH but they are not added as projects so I don't get any findings in the Problems view 👍
image

But still, I would like to test it out on Mac before we close this issue (I don't have it on me right now) since that's where the error happened.

@merks do you think this could be related to some kind of caching issue? I usually don't develop on my Mac so chances are that the caches there are totally outdated. BTW I followed your instructions when I installed the (faulty) Eclipse in my Mac and I will do so tomorrow when I test it again :)

@fedejeanne
Copy link
Contributor Author

Same thing in my Mac, the error is not reproducible...

I don't know how I got those "projects" imported into my WS, I must have cloned the Git Repos after the installation and wrongly searched for nested projects and forgotten about it.

@merks sorry for the confusion and thank you for your support!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants