In jdee-server's github, It says
Copy target/jdee-bundle-${version}.jar to a directory and customize jdee-server-dir to point to the dir.
But I can't understand it. What is target/jdee-bundle-${version}.jar?
I install jdee using emacs melpa, it doesn't have such file.
In the current pom.xml maven file in the github repository, you can see that the jdee-server version number is:
<version>1.0-SNAPSHOT</version>
According to the README file in the repository, this means the resulting jar file will be named target/jdee-bundle-1.0-SNAPSHOT.jar. But when you build jdee-server following its README instructions, you'll get two jar files:
target/jdee-1.0-SNAPSHOT.jar
target/jdee-bundle-1.0-SNAPSHOT.jar-jar-with-dependencies.jar
Copy both files to a directory of your choosing, then in your emacs startup file set jdee-server-dir to the name of that directory. For example, if the directory you choose is /home/ttong/jdee-server, set jdee-server-dir like this:
(setq jdee-server-dir "/home/ttong/jdee-server")
Related
I try to execute a jar file in the command prompt, but I always get the message 'no main manifest attribute, in 2056751-0.0.1-SNAPSHOT-src.jar'. So, I guess I should edit the manifest file. If I check it in the command prompt with the command 'jar tf 2056751-0.0.1-SNAPSHOT-src.jar' I can see that there is a MANIFEST.MF file, still I cannot see it in Eclipse project view.
To partially answer the question asked, IF on Windows (which you didn't say and isn't the only system with a command prompt), a jar file is really a ZIP file underneath and Explorer in all supported versions (>XP/S03) can treat a ZIP file as a directory subtree, so just rename to have the extension .zip and open in explorer, go to META-INF, select MANIFEST.MF and open with plain-text editor of your choice such as notepad. However this may not allow you to edit; if so copy to somewhere writable like the desktop, edit, then copy or move back. Then rename back to .jar
Although the manifest file in a jar can be loaded from an actual file, usually it is created by the jar tool. If you want a jar containing classes to run from the usual file association on Windows use the jar tool with the e option as described in the man page or Windows version on the web and help message. However if your file name is accurate and this is actually a source jar, it will never be runnable by only changing the manifest and you need to learn how Java works.
Is it possible to create Eclipse-style folders (Project Folder, Package and so on) via the Terminal?
I once renamed an Eclipse package like this: mv oldname newname, and I noticed that after doing so, Eclipse no longer considered the folder a Package.
This possibly means that it is a matter of metadata, but I have so far been unsuccessful in locating the files containing the relevant information.
Eclipse does not provide anything to do this and it is not really possible manually.
For a project some information is stored in the .project file in the project folder. Depending on the type of project there may also be a .classpath file and there will also be data stored in the .metadata folder in the workspace and also in a .settings folder in the project.
All the file and folder names starting with . are considered to be hidden on Linux, Unix and Mac systems and are not shown by default. Use the -a flag of ls to see them.
When you add a folder in eclipse using link a source directory we can use variables. I need to know where these variables and their values are stored. Is it in a configuration file?
I followed the below , Went to eclipse, (java) project properties, and then java build path.
Now I clicked on link source and added a variable - say top_root and pointed to a location say - c:\temp
I used the same to link a source directory. This information is available in .project file.
I need to know, in which file test=c:\temp will be configured / available.
<link>
<name>java</name>
<type>2</type>
<locationURI>top_root/src/java</locationURI>
</link>
eclipse-3.5.2\workspace\\.metadata\\.plugins\org.eclipse.core.runtime\\.settings\org.eclipse.core.resources.prefs
The configuration was available, Inside the above folder, this file org.eclipse.core.resources.prefs
pathvariable.top_root=C\:/temp
search for all prefs files
In my Eclipse Java Build Path, I set Source Output Folders to:
WEB-INF/classes
and I put the config file globals.conf in this folder.
When I run Project - Clean, my config file globals.conf is gone
How can I keep my config file when I run Clean?
globals.conf should be putted under source folder, not source output folder.
Eclipse will copy all resource files(not *.java) in source folder into output folder.
Our team has just moved from Netbeans to IntelliJ 9 Ultimate and need to know what files/folders should typically be excluded from source control as they are not "workstation portable", i.e.: they reference paths that only exist on one user's computer.
As far as I can tell, IntelliJ wants to ignore most of the .idea project including
.idea/artifacts/*
.idea/inspectionProfiles/*
.idea/copyright/*
.idea/dataSources.ids
.idea/dataSources.xml
.idea/workspace.xml
However, it seems to want to check in the .iml files that exist in each module's root directory.
I originally checked in the entire .idea directory via the command line which is obviously not aware of what "should" be ignored by IDEA. Is the entire .idea directory typically ignored?
We have a FAQ article covering this question.
[The .idea] format is used by all the recent IDE versions by default.
Here is what you need to share:
All the files under .idea directory in the project root except the workspace.xml and tasks.xml files which store user specific settings
All the .iml module files that can be located in different module directories (applies to IntelliJ IDEA)
Be careful about sharing the following:
Android artifacts that produce a signed build (will contain keystore passwords)
In IDEA 13 and earlier dataSources.ids, datasources.xml can contain database passwords. IDEA 14 solves this problem.
You may consider not to share the following:
.iml files for the Gradle or Maven based projects, since these files will be generated on import
gradle.xml file, see this discussion
user dictionaries folder (to avoid conflicts if other developer has the same name)
XML files under .idea/libraries in case they are generated from Gradle or Maven project
.idea directory is a replacement for the old .ipr (Idea Project) file and if you want to share the project between users, then you need to share .idea folder (with the exceptions mentioned in the FAQ) and all the .iml files.
Refer to GitHub's JetBrains.gitignore file to always have an updated listing of which files to ignore.
Not an exact answer to the question, but there are sample .gitignore files available here, including one for JetBrains which includes IntelliJ.
You might find this post interesting: Merges on IntelliJ IDEA .IPR and .IWS files
It seems to conclude that you should add all files except for: workspace.xml, dataSources.xml, sqlDataSources.xml and dynamic.xml. The answer there is focusing on having files that do not change simply from opening the editor or making ide specific changes.
I'm using PHPStorm.
Here is an example snippet for your .gitignore
# Ignore the following 2 PHPStorm files only workspace and tasks file
**/.idea/workspace.xml
**/.idea/tasks.xml
All other files in the .idea directory should be committed to your repository.
e.g: (commit everything else in the .idea directory)
new file: .idea/.name
new file: .idea/encodings.xml
new file: .idea/framework.iml
...
Docs: How to manage projects under Version Control Systems
Here is what you need to share:
All the files under .idea directory in the project root except the workspace.xml and tasks.xml files which store user specific settings
All the .iml module files that can be located in different module directories (applies to IntelliJ IDEA)
So basically, commit everything except workspace.xml and tasks.xml.
Yes, I believe so. You can check the SVN configuration to see what's ignored and add anything that you think should be ignored.
IntelliJ now creates its own .gitignore file in the .idea folder so you can safely add it to repository.