Install Eclipse IDE
Install Eclipse IDE
See: [1]
Steps:
- Download *.tar.gz from Eclipse
- Open tar.gz as Administrator and extract to /opt/eclipse4.3.1
- Open terminal:
- cd /opt
- sudo chown -R root:root eclipse4.3.1 # -R : recursive
- sudo chmod -R +r eclipse4.3.1 # +r : add read flag
- sudo chmod +x `sudo find eclipse4.3.1 -type d` # set execute flags on directories (?)
- cd /usr/bin
- sudo touch eclipse4.3.1
- sudo chmod 755 eclipse4.3.1
- paste following code into 'eclipse4.3.1':
#!/bin/sh- export MOZILLA_FIVE_HOME="/usr/lib/mozilla/"
- export ECLIPSE_HOME="/opt/eclipse4.3.1"
$ECLIPSE_HOME/eclipse $*
- Create menu item:
- right click on menu-bar, Edit Menus
- under 'Programming' create 'New Item':
- Type: application
- Name: Eclipse
- Command: eclipse4.3.1
- Comment: Eclipse IDE
- Icon: /opt/eclipse4.3.1/icon.xpm
- /opt/eclipse4.3.1/eclipse -clean
Subversion with Subversive PlugIn
- Install 'Subversive SVN Team Provider' and 'Subversive Revision Graph' via 'Help', 'Install New Software...', '--All Available Sites--'
- Restart, now a dialog should appear to install SVN connectors. It may case this dialog just disappeared and I installed a connector as follows:
- 'Help', 'Install New Software...', 'Add...': enter 'Subversive' and 'http://community.polarion.com/projects/subversive/download/eclipse/3.0/kepler-site/', OK
- install SVNKit connector implementation, restart as requested
Vaadin PlugIn
- 'Help', 'Install New Software...', 'Add...': enter 'Vaadin' and 'http://vaadin.com/eclipse', OK
- install Vaadin Plugin and restart
Install Groovy Support
- Open Eclipse as admin (sudo eclipse, according to an error in Eclipse, the plugin installation must be done as root.)
- Help, Eclipse Marketplace..., Search for Groovy, Install
Doesn't work:
- Help, Install...
- Enter 'http://dist.springsource.org/release/GRECLIPSE/e3.7/' then enter "Groovy" in dialog (doesn't matter)
- press 'Select all', 'Next'
IvyIDE
See Ivy
FindBugs
FindBugs is a good static Java code analysis tool. You can install it via Help, Eclipse Marketplace... To run right-click on your Java project and select 'Find Bugs', 'Find Bugs'. You can run it automatically if you open the project settings (Alt-Enter), 'Find Bugs', 'Run automatically'.
See for more FindBugs Manual.
Using FindBugs and Parboiled parser library together in one war produced a difficult to sort out error! Using them together in JUnit-tests did not show an error. Reason how it came to this effect:
- FindBugs recognized recursion in parser code which is true from first sight. Since Parboiled does some code manipulation on class level the recursion is resolved and not an issue altogether. (Parboiled uses Java for defining the lexicographical rules.)
- For suppressing the FindBugs error the FindBugs library were needed to import in the classpath.
- Since Parboiled and FindBugs use different versions of the ASM library running the whole application failed. (Parboiled needs 4.1, FindBugs 3.1.)
I suppose when using the Parboiled preferred ASM library only the problem could be solved... (Currently FindBugs is not on the classpath and hence the recursion warning not suppressed.)
OLD CONTENT
GIT
Links:
The question to use GIT or Subversion may be a hard question. It resulted in:
- When using RedHat OpenShift, you need get used to GIT.
- GIT is already installed in Eclipse Indigo.
- I wouldn't need the distributed developement GIT offers.
- Why use GIT and subversion in parallel?
So I am now using GIT! (Assembla supports GIT and Subversion hostings...)
A helpful tool may be Rabbit VCS. I had to install via tarball:
- sudo apt-get install python-nautilus python-configobj python-gtk2 python-glade2 python-svn python-dbus python-dulwich subversion meld
- Download rabbitvcs-0.15.0.5.tar.bz2 and untar it into a temp folder.
- Install base RabbitVCS: sudo python setup.py install --install-layout=deb
- Once that is done working, look in the clients folder and read the README file for each client/plugin to learn how they are installed.
- gedit: After copied the necessary files (see README) you have to enable the plugin in gedit: Edit, Preferences, Plugins: check 'RabbitVCS'
Assembla
If you create an Assembla account you get all the tools for free for 30 days. Afterwards you have to downgrade. Nevertheless this is not really a problem, all your code stays there. How to:
- Add a 2nd (GIT-)repository?
- Click 'Admin' tab, then 'Tools', 'Add another' 'Git/Source' -> Here you go!
Install Subversion Support
Book about Subversion: [2]
Good introduction: [3]
(and see [4] / [5])
- Setup subversion(or GIT...) account in e.g. Assembla or Freepository, see Wikipedia for other repositories. (You can set up a local Subversion server as well...)
- Open Eclipse as admin (sudo eclipse, according to an error in Eclipse, the plugin installation must be done as root.)
- 'Help', 'Install New Software..', 'Add host' http://subclipse.tigris.org/update_1.8.x, add everything for Subclipse, install it, then terminate Eclipse.
- Now you should start Eclipse as user again. Probably this produces the error, that the JavaHL is missing:
- You can try to install libsvn-java by means of Synaptic Package Manager. This may fail since JavaHL is expected to be used in a newer version. (This was the case since I used a newer version of Eclipse than Ubuntu configured.)
- In this case download "CollabNet Subversion Edge 2.2.1 (for Linux 32 bit)" (file CollabNetSubversionEdge-2.2.1_linux-x86.tar.gz) from CollabNet (See StackOverflow.) For this, you need to register in CollabNet...
- Move to /opt and unzip with: sudo tar zxf CollabNetSubversionEdge-2.2.1_linux-x86.tar.gz. (CollabNetSubversionEdge-2.2.1_linux-x86.tar.gz can be deleted afterwards.)
- Add following line (as Admin) to /opt/eclipse/eclipse.ini: -Djava.library.path=/opt/csvn/lib
- Restart Eclipse as user. Now an information may occur that the password cannot be set in the keyring. Press OK.
Further experienced "challenges":
- If you started Eclipse as root and refreshed some projects the content of the bin-directories may be created with user 'root' and may produce errors now: just delete them.
- <user>/.subversion was created under user 'root'. I changed this by issuing: sudo chown -R pfu:pfu .subversion
- Some directories under <user>/workspace/.metadata were created under user 'root'. I changed this by issuing: sudo chown -R pfu:pfu workspace/.metadata
SVN-client: Install 'kdesvn'