In which file eclipse "deployment assembly" configurations are at? - java

I can't seem to find this configuration at .project file. I am looking for a way to change this setting programmatically as "I don't know why" my eclipse is losing this configuration every time I clean the project.

The deployment assembly settings are stored in the file:
.settings/org.eclipse.wst.common.component
However, in a basic J2EE Eclipse install this file shouldn't be modified by cleaning the project. Maybe you have some other plugin installed that is updating the deployment settings during the build.

I faced the same problem and the reason being that the file .settings/org.eclipse.wst.common.component contained entries added by Git. On removing them, and restarting the eclipse worked for me.

Related

Stop Eclipse/Gradle from generating .project and .settings/

I once installed Eclipse a few days ago on my Ubuntu machine and decided to remove it, but now there's a .setting/ directory and .project file in my android project repository and it is generated again after removing it using rm command. How should I stop it?
Perhaps your build.gradle file has the Gradle Eclipse plugin referenced? This would be the only reason why those files keep getting generated even if you stopped using Eclipse. If this is the case, compare your Gradle build to a previous version, or simply remove the Eclipse plugins.
If you are still using Eclipse, or any Eclipse based IDE, those files will keep getting generated and I wouldn't recommend deleting them. As suggested earlier, you can prevent them from getting into your source control system. If using Git, you can add the following to your .gitignore file to have these files ignored.
.project
.settings

Eclipse referring old class files of Maven. Have to re-build the project everytime I make a single change

I am using Maven projects in my Eclipse workspace.
But, somehow Eclipse is referring the old .class files while running the program.
Hence, I have to re-build the complete project everytime I make any change to any java program.
I have tried executing maven commands like eclipse:clean & eclipse:eclipse.
But, they did not help.
My eclipse is also set to project - build automatically.
Is there a way I can tell Eclipse to refer to the current built .class files and not the previously built maven .class files.
Note: I am using Eclipse Mars
Thanks in advance.
I am afraid. There is no way to doing it automatically. Even if you find a way to do so. There isn't any guarantee that eclipse will build with new war.
Either you go for manual mvn clean install or use intellij idea it is very much statble. No build issue. Every time on your single save it will build new war file.
Posting answer to my question:
Sometimes the .project file of Eclipse gets corrupted. Easy solution is :
Delete the project from Eclipse.
Close Eclipse.
Go to your project's folder and delete ".settings, .project, .classpath, bin"
Open Eclipse again, and import your project once again.
This way it always works.

Installing Eclipse RCP Plugins

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?

Why can I not add .jar to eclipse git repo?

I am using Eclipse Kepler for Java. Normally you can add internal/external .jars to a Java project in the build path located in the properties. Why, when I clone a git repo and import it into my projects, do I lose that ability? I don't understand. I kinda need to do that.
This is probably because the .gitignore has been configured to ignore .jar
Open the .gitignore file and remove the line *.jar, you should be able to add it.
======
As an aside - usually, for Java projects .jar files are not committed to repository (as they are large & it can slow down repository cloning), instead maven or gradle is used to configure dependencies. Example - http://www.mkyong.com/maven/how-to-create-a-java-project-with-maven/
Then when you want to work with eclipse just run mvn eclipse:eclipse to generate the necessary files. .gitgnore is usually set up to ignore *.class, *.jar, .project, .settings, .classpath
I found that if you open the run configurations and go to the Classpath tab that you can add internal/external .jars. The run configuration can be accessed by clicking Run > Run configurations. I added my .jar to the user entries. The bootstrap entry caused a null pointer.
When a project relies on libraries/modules, it's best to use a build tool for dependency management. JVM ecosystem is dominated with three build tools: Gradle, Maven and Ant.
How it works:
In a build script we declare dependencies of the project. This tells the build tool where to retrieve libraries/modules our project depends on. Dependencies are resolved at runtime; downloaded from a remote repository, retrieved from a local directory or if required another project to be built in a multi-project setting.

SVN Eclipse ignore folders for all users

I recently created new project with maven and committed on SVN server from Eclipse. Everytime i build this project SVN wants to commit also .settings, .project and some other files form target folder. I have succeeded to make SVN ignore from eclipse but it will work only for me.
How to make a "global" svn ignore that would work for all svn users? Can it be done only from svn server or it is a possibility that i can do it from my svn client?
Please suggest any working solutions :).
Best Regards.
You should use the svn:ignore property instead global configuration change. You have to edit/add the svn:ignore property to your trunk folder and should have the following content:
target
.settings
.classpath
.project
This can be done using your svn client.

Categories

Resources