Closed mikadou closed 4 years ago
Ok, I solved my problem. The error was on my end and had nothing to do with vscode-pde.
First, I had to modify the build.gradle
script to add the org.eclipse.pde.PluginNature
to the .project
file.
Second, I had to add a META-INF\MANIFEST.MF
file which lists dependencies under the Required-Bundle
entry.
Good to see you fixing it yourself.
Hi, I'm not sure if what I want to achieve can be done with vscode-pde. I'm still new to PDE, OSGI and all this stuff. I have a ordinary (non-OSGI) Java command line application. The application depends on some jar-files in a local directory which is defined in the Gradle build. Everything builds and works as expected.
Now, I would like to navigate the code in VSCode including the dependencies. The sources of the dependencies are located in a local p2 repository. At least that is what I think it is. It is a directory that contains artifacts.jar, content.jar and subdirectories with src.zip files.
Here is what I have tried so far:
target.target
file to my project folder. It is pointing to the p2 repository.classpath
After updating the project configuration the
.classpath
file contains the classpathentrytarget.target
file and execute Reload Target PlatformIs there something I am missing in order to get this to work?
BTW I tried to figure out by myself how Reload Target Platform works behind the scenes, but I failed to understand where
java.pde.reloadTargetPlatform
is defined. It is executed in this line.