-
Notifications
You must be signed in to change notification settings - Fork 58
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
Remove Maven Artifacts from the target #851
Remove Maven Artifacts from the target #851
Conversation
Remove Maven Artifacts from the target, as the lastest version of PDE cannot resolve them.
PDE needs M2e PDE feature being installed (https://www.eclipse.org/downloads/download.php?file=/technology/m2e/releases/2.4.0/features/org.eclipse.m2e.pde.feature_2.2.200.20230820-0922.jar ) in order to resolve Maven directly. Do you have it installed? |
Would you please try to edit the feature (without changing anything) to force pde to re-resolve it? |
I have increased sequenceNumber, saved and refreshed. Same problem. |
I tried that already, it did not work either. Creating a new workspace and importing the lsp4e project again, and loading the target file in the new workspace did not work either. |
I reproduce it with lsp4e. Please give me few hours to investigate before pushing this one. I'll get back here. |
@akurtakov , it is a missing feature (#849 (reply in thread)), I would suggest that we merge this PR then, as it is very inconvenient if people clone our repo and cannot work with it out of the box, and I do not see any drawback of using just p2 locations. Do you agree? |
OK. Go for it. |
Remove Maven Artifacts from the target, as the lastest version of PDE cannot resolve them.