I am developing an eclipse plugin and facing a deployment problem:
After zipping the whole eclipse plugin and installing it on eclipse using Help--> Install New Software--> from archive file, once I would like to uninstall it through Help --> About Eclipse Platform --> Installation Details --> Installed Software --> Uninstall..., the old jar files will remain under eclipse/plugins folder. And when I try to install a new version of the eclipse plugin, the previous jar files are not overwritten by the new ones.
Is anything wrong within my process? does anyone has an idea about deploying eclipse plugins properly? thanks!!!
To get rid of the old plugins you have to clear the Installation History. Go to Help | About Eclipse | Installation Details | Installation History and select all the old stuff. Then click delete and restart. Now install the new plugin.
The other way to achieve this is by copying the corresponding directory (or jar) from the source eclipse install plugins/ or/and features/ directory to the target eclipse install plugin/ or/and features/ directory
Related
I am not having any luck searching for a solution to this problem.
I work with a team that uses Eclipse for the java IDE, and gradle for the project build. We are developing on a linux distro.
One of the Java projects needs to use library jar files that gradle pulls down into the {homedir}/.gradle/cache directory tree.
How do I setup the project Build Path in eclipse, and the .classpath file it generates, to use a home directory variable ({HOMEDIR_VAR}/.gradle/cache/...), instead of hard-coding my home directory (/home/{myusername}/.gradle/cache/...)?
It is usually a good practice to not commit IDE specific project files to version control. Modern build tools (Maven, Gradle) integrate nicely with IDEs like Eclipse, IntelliJ IDEA and Netbeans to generate those artifacts for you.
In short, let Gradle build the Eclipse class path for you. That is either via
Buildship (Using the Gradle build system in the Eclipse IDE - Tutorial), the official Eclipse plugin to integrate with the Gradle build system. Easy to use and you can directly import Gradle projects into Eclipse.
Gradle Eclipse Plugin, a Gradle plugin that generates required Eclipse project files.
There's no need to fiddle with the class path manually anymore. However, if for somewhat reason this doesn't work out for you, there's a workaround: It is possible to relocate the Gradle home directory and with that the cache directory to a static path. This can be done for example by defining the environment variable GRADLE_USER_HOME (Gradle Goodness: Changing the Gradle User Home Directory). With that, it's possible to maintain the Eclipse class path manually and share it with your team.
I'm new to java . I'm using eclipse. I want to create database project using derby . I installed two files for derby called derby_ui_doc_plugin_1.1.3.zip and derby_core_plugin_10.8.2.zip and extracted them in plug ins of eclipse but when I opened the eclipse I couldn't find data management or data source or anything that told me that derby is installed . Thanks in advance
i'm working on Kepler Service Release 2 if version is old . how can i update it ?
These plugins are very old and are not supported by current versions of Eclipse.
Derby no longer provide a UI or plugins for Eclipse. You can still use the Derby jars in plugins but without the UI.
To use the Derby jars in an Eclipse plugin include them in the plugin folder and add the jars to the plugin classpath. You do this by opening the MANIFEST.MF editor and add the jars to the 'Classpath' list on the 'Runtime' tab.
I have an Eclipse RCP application that I would like to install a plugin into. I know the plugin works with the application, and with older versions of the application I could just drop the plugin JAR into plugins/ folder and it would be available next time I loaded the application.
However, with the current version, the JAR doesn't seem to get picked up when I put it in the plugins/ folder. I've tried running the application with the --clean flag, but that doesn't help.
How do I tell the application that I want to install the plugin?
Update: Got it working by adding the plugin to the config.ini - I've not needed to do that before, previously it would just be picked up when I placed it in the plugins/ folder. Is there a configuration option that disables the detection of new plugins from the plugins/ folder?
#Fredrik basically says it: You need to put the plugin in the "dropins" folder, the sister directory to the plugins directory. Then restart. I usually run eclipse -clean just to be safe. If there's a problem with the plugin, you will need to using the p2 debugger as mentioned in https://stackoverflow.com/a/12480978/2295812
Got it working by adding the plugin to the config.ini - I've not needed to do that before, previously it would just be picked up when I placed it in the plugins/ folder. Is there a configuration option that disables the detection of new plugins from the plugins/ folder?
This question already has answers here:
How do I import the javax.servlet / jakarta.servlet API in my Eclipse project?
(16 answers)
Closed 6 years ago.
I have a project that requires some Tomcat libs to run properly. I installed Tomcat (on Mac) which is essentially just a put-the-folder-somewhere process. I originally resolved the issue by adding the needed jar files as external jars for the project - however this messes with the project .classpath which I can't allow - those changes would be tracked in our source control.
I've tried adding the tomcat/lib directory to eclipse as a classpath variable but that doesn't resolve the issue.
When the tomcat server starts, I receive ClassNotFoundException: HttpServletRequest.
How else can I add the tomcat lib directory so that I'm not modifying the project classpath?
You can install Webtools plugin (installed by default in Eclipse for JavaEE Developers) and then you will get Tomcat runtime support. Then you can add a "Tomcat Runtime" to your project and it will automatically include all Tomcat jars that are available to webapps running on Tomcat.
Window > Preferences > Server > Runtime environments
Add..
Select Tomcat version
Browse to tomcat install dir
Right click you project > Properties
Select Java Build Path
Add library... > Server Runtime > select your runtime you created
This process will also modify your .classpath file but it will do so in a way that is easy to share with other developers.
Maybe you can create an user library which include the jars in the tomcat/lib, then add the user library in your java projet by those steps :
Build Path > Configure Build Path > Libraries > Add library > Add user library
I use sysdeo tomcat plugin found at http://www.eclipsetotale.com/tomcatPlugin.html. You can also install it by going to Help->Eclipse Marketplace->search for sysdeo
What it does is add a menu item called tomcat in your options that allows you to add projects to tomcat classpath and add tomcat libs to your project pre-compile.
Heres some screenshots of it.
starting and stopping tomcat is made easier:
and where you can add the libs to classpath (and much more)
I've had this problem several times while using subversion with windows users. The Tomcat directory will have servlet-api.jar.
Copy and paste it in your eclipse project, right click and add to build path.
Now you don't want to commit the classpath. Then simply deselect .classpath file while committing.
basically i am using windows i dont know about that, but you can do that from eclipse right click on your project in eclipse then see there is a build path from that import(some thing like that) server's(tomcat) lib file where you have install server and put all libs file if you want all
I got an Maven project which is compiled in Eclipse. Now I need to migrate it to a Linux environment, and there won't be GUI interface I can use. I wonder what I should do to migrate it?
Currently , under Eclipse project folder I have the files/folders as the below:
.classpath
.project
.settings
.springBeans
doc
pom.xml
src
target
I figure all those .* folders are Eclipse meta data. so I can remove them. Then I can use the rest to form a Maven project that I can build using Maven command lines?
For a maven project to work command line, all you need is
Maven is installed and correctly exported in the $PATH variable
The pom.xml in your workspace.
Just go to the project directory and run mvn install.
mvn clean
then remove .project .classpath
if you want to lose eclipse project settings while migrating delete .settings (assuming it doesn't have machine specific path/settings)
copy rest to new linux environment
open eclipse, import project as maven project (assuming you have new eclipse with maven plugin setup on linux environment)
Note:
make sure you still have a backup before you successfully migrate over
.classpath contains references to local .m2 when used with eclipse and maven so the path would differ in linux and would create issue
.project contains some configuration that is eclipse maven plugin dependent, so it is good to loose it once and let new environment create new one