unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Leo Liu <sdl.web@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: java develeopment
Date: Wed, 20 Mar 2013 19:31:53 +0800	[thread overview]
Message-ID: <m1hak6qpcm.fsf@gmail.com> (raw)
In-Reply-To: 86a9py4a3s.fsf@fastmail.fm

On 2013-03-20 18:52 +0800, Filipp Gunbin wrote:
> I use the following (very minimal) tools:
>
> 1. Etags for navigation. While it's not convenient to update tag tables
> frequently, it's rarely needed for me. I usually generate a single tag
> table for a whole project instead of a separate one for each module. It
> allows to quickly find a class/method and I'm fine with it.

I am a casual java user. I use GNU Global + ggtags¹ for java.

I have

  export GTAGSLIBPATH=/usr/local/unix/java/1.6/classes

to point to the java sdk's classes source and from then on can jump to
any class/method in my project including those in SDK. This solves the
jump-to-definition (source code navigation) problem for me. See this
screenshot: http://i.imgur.com/d430rmm.png

You can get some completion (see ggtags-tag-names) from the database
built by GNU Global but it won't be as good as precise code completion.

HTH,
Leo

Footnotes: 
¹  http://elpa.gnu.org/packages/ggtags.html




  reply	other threads:[~2013-03-20 11:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-19 14:12 java develeopment Rich Johns
2013-03-19 19:27 ` Dmitry Gutov
2013-03-19 19:38 ` Thorsten Jolitz
2013-03-19 20:02   ` Rich Johns
2013-03-20 13:15     ` Thorsten Jolitz
2013-03-20 10:11 ` Phillip Lord
2013-03-20 10:52 ` Filipp Gunbin
2013-03-20 11:31   ` Leo Liu [this message]
2013-03-21 13:33   ` Rich Johns
2013-03-22  8:42   ` David Banks
2013-03-23  7:55     ` Filipp Gunbin
     [not found] <mailman.22486.1363717911.855.help-gnu-emacs@gnu.org>
2013-03-21  7:01 ` Pascal Quesseveur
  -- strict thread matches above, loose matches on Subject: below --
2013-03-31 19:09 Barry OReilly

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m1hak6qpcm.fsf@gmail.com \
    --to=sdl.web@gmail.com \
    --cc=help-gnu-emacs@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).