I'm new to programming and I'm currently facing this problem.
[I leave here some pictures](https://i.stack.imgur.com/G35lr.png)
I tried downloading some files that I find on Internet searching the problem but it remained the same.
This are the files
Thanks for the help
There's a strange dependency problem happening as the platform moves to packaging SLF4J directly from Maven and recommended everyone else not require the bundle be present in their own features, resulting in some installations not having it when they should. Don't worry if that doesn't explain anything to you, a possible workaround is to manually install the bundle using the CLI, after exiting the IDE:
eclipse.exe -application org.eclipse.equinox.p2.director -repository https://download.eclipse.org/releases/latest -installIU org.slf4j.api
Related
I've searched through several related topics here on StackOverflow, but the solutions do not work for me. I've added the -D parameters to my jvm in Eclipse.ini, specifying the keystore and truststore (both cacerts on my machine) and their passwords. Still, I can only get dependencies to download on the command line and Eclipse continues to complain about PKIX errors. I need to make Eclipse do the right thing in a global fashion; our dependencies will always come from our internal repository, which is a mirror for the public repositories as well as hosting our internally produced dependencies. Help is much appreciated!
Not sure how to mark this as answered so it doesn't bother anyone else. I had to restart Eclipse more than once for it to see the ini file changes. Not sure why though.
I will be glad, if my eclipse didn't have the mylyn and the cvs modules. I don't want them, I want them to get out. But the eclipse package management doesn't let me their removal.
I tried already to remove them from the packages & features directory, but it didn't work.
An ideal solution were, if existed some flag or settings in the eclipse packages, which contained the information from a package if it is removable.
Yes, I know that eclipse loads these packages only on need, but I want to remove, delete them forever and sow their place with salt.
Harsh. The simplest thing to do then is to start with the bare Eclipse Platform Runtime Binary download then add the things you do want.
http://download.eclipse.org/eclipse/downloads/drops4/R-4.3.1-201309111000/
Build your custom installation by using the p2.director application (from an SDK download) to install exactly those features you like to have. p2.director help
General description (accessing all kepler simultaneous release repos). Mind the the appendix <.feature.group> for features you want to install.
c:\<eclipse-sdk>\eclipsec.exe -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/eclipse/updates/4.3,http://download.eclipse.org/releases/kepler,http://download.eclipse.org/technology/epp/packages/kepler -installIU <feature1>.feature.group,<feature1>.feature.group,<bundleX>,<bundleY> -destination c:/eclipse -profile SDKProfile
concrete example installing only the SDK on windows (be patient for the download)
F:\__TEST\eclipse-SDK-4.3-win32-x86_64\eclipse\eclipsec.exe -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/eclipse/updates/4.3,http://download.eclipse.org/releases/kepler,http://download.eclipse.org/technology/epp/packages/kepler -installIU org.eclipse.sdk.ide -destination c:/eclipse -profile SDKProfile
You find the resulting installed product inside the destination c:/eclipse.
I'm trying to deploy a few bundles I implemented along all the required bundles from Eclipse in order to run my own. Let's say, include the Equinox container also with my bundles so it is like an executable old-school JAR.
That said, when I try to run
java -jar org.eclipse.osgi_3.8.1.v20120830-144521.jar
Nothing happens...it just stays there doing nothing...even if I copy just that bundle to some other place and try the same, nothing happens...is this usual? I mean, I have done this successfully with older versions of this bundle (3.6) and it worked flawlessly.
Alas, I tried -debug flag to see if I could get some output, but only a complain about mission .options file is happening, nothing else.
Thanks,
Alex
Just in case someone has the same problem...having checked this link: http://docs.codehaus.org/spaces/flyingpdf/pdfpageexport.action?pageId=82903240, I created the configuration folder, a config.ini in it with the following contents:
osgi.bundles=org.eclipse.equinox.common#start, org.eclipse.update.configurator#start,
org.eclipse.core.runtime#start, org.eclipse.core.jobs#start,
org.eclipse.equinox.registry#start, org.eclipse.equinox.preferences#start,
org.eclipse.core.contenttype#start, org.apache.felix.gogo.runtime#start,
org.apache.felix.gogo.shell#start,
org.eclipse.equinox.app#start,org.eclipse.equinox.console#start,
eclipse.ignoreApp=true
osgi.noShutdown=true
This seems to work. I believe this is the minimum set of bundles required to run the Equinox OSGi container...from there, you can use the osgi shell to play with your bundles
You havent included -console option, that is the one that will open up the console view right?
What could cause Eclipse to ignore plugins in the dropins catalog?
I've created a dummyplugin based on the Eclipse wizard, exported it to a jar. When dropping it into the drop-ins catalog of a fresh Eclipse installation, it works fine.
When I do the same thing but on a custom Eclipse installation, it doesn't work. The plugin doesn't even show up in the plugin registry view. No error messages or anything like that.
I've tried:
Running with -clean
Running with -clean -consoleLog but no errors were printed
Starting up with -console, and checking if the plugin is seen with the command ss, no luck.
Running with -Dorg.eclipse.equinox.p2.reconciler.dropins.directory=C:\Program\Eclipse\eclipse3.6\dropins\
Changing name of the eclipse catalog from eclipse3.6 to eclipse, in case I had run into a variation of an Eclipse bug
It's not due to dependency issues (like this question), since the plugin isn't even found
Update Copied the eclipse.ini from the working eclipse installation to the custom one, with the same result; The plugin wasn't found. So the issue isn't in the ini file
Update Thought the issue might be some rights issue, since I my user wasn't the owner of the custom installation. So I made a copy of the entire dir of the custom installation to make sure I was the owner with full rights. No change
Update Starting with a new workspace doesn't make any difference
Is it possible to define that Eclipse should ignore the dropins catalog? How?
The custom version of Eclipse defines a lot of variables, but nothing that seems related to p2 or the behaviour of dropins.
The dropins/ folder is a best effort, totally optional, silently failing legacy leftover. Not big on the diagnostics, as you've found.
If you use the director to install your bundle into your custom eclipse, at least you'll be able to get an error message that will tell you what the problem is.
I'd suggest exporting your jar with some minimal p2 metadata.
Then you use something like:
eclipse/eclipse \
-application org.eclipse.equinox.p2.director \
-noSplash \
-repository \
file://$HOME/eclipseUpdate \
-installIUs \
org.dojotoolkit/1.6.1.v201105210659
If p2 can't find some dependency, it should spew out the confusing error messages it can generate.
Hi #Fredrick I've made my own plugin and I've added to my eclipse in this way:
Export the plugin as Deployable plug-ins and fragements.
(Right click on the plugin project - Export - Plugin Development - Deployable plug-ins and fragements)
That will generate a .jar file that file you have to copied into \eclipse\plugins
Restart eclipse.
I'd say that will be all.
I've got an ANT project with libs managed by ivy (they are under lib_managed). Eclipse is using the jars to. Probelm is: if I try to update the directory ant refuses to delete it because eclipse holds on to the jars in its classpath. Even if I update (empty) eclipses classpath I can't delete the files. If anyone had the same problem and found a solution I would be thankfull for an answer.
Regards, Jan
Not a solution, but a workaround. I experience Eclipse keeping locks on files quite often in different contexts. I suggest using Unlocker.
I guess this is on Windows. Use the Process Explorer to figure out who is locking the files. Eclipse shouldn't keep a lock; maybe you have the code running in the debugger (hanging in a breakpoint). Use the list of open files and the properties to figure out which Java program is keeping the lock on the files.
If it's really Eclipse, try to upgrade to a newer version of Eclipse or close the project when you need to update the dependencies with ivy.
Cleaning the workspace and restarting eclipse may solve the problem. But in real development environment i don't think its a good idea to restart eclipse whenever you need to build a jar.