>>>>> "Przemysław" == Przemysław Wojnowski <espera...@cumego.com> writes:
Nice list Przemysław. I can see common themes between Paul's
original list and the user features people seem to want. Leaving aside
the question "to fork, or not to fork?" here are some observations.
Przemysław> 1. Easy installation and configuration No one will use
Przemysław> JDEE if it takes a weekend to make it up and running.
Przemysław> For example available JDKs (jde-jdk-registry) usually
Przemysław> can be setup automatically from: JAVA_HOME, default
Przemysław> paths in OS (/usr/lib/jvm, "C:\Program Files\java",
Przemysław> etc.).
The detection of available JDK works *except* for gnu/linux systems that
use /etc/alternatives. I have a fix that I will commit this weekend for
gnu/linux that should solve it (at least on the systems I have). But on
recent Mac OS X systems, or if you set JAVA_HOME, it should Just
Work. Bug reports/patches always welcome.
Przemysław> 2. Integration with build tools (especially Maven) By
Przemysław> that I mean loading project configuration (source/test
Przemysław> classpaths) form build tool definition - pom.xml in case
Przemysław> of Maven. This is a must for any non-HelloWorld
Przemysław> project.
Right now it only works with ant (and, IMHO, extremely well - on ant
based projects JDEE is the best way to use Emacs). Yes, I need pom.xml
parsing too. I will attempt to add it as soon as I have the time, or if
some one sends me patches that work :-)
Przemysław> 3. Code completion IMHO from this point JDEE
Przemysław> can be used at all.
Which parts of "C-c C-v ." (jde-complete-in-line) or (jde-complete-menu)
are you unhappy with? I really want to know so it can be improved, and
it works for me. Yes, I wish we had generics support too....
Przemysław> 4. Jumping around the code - back and forth. To
Przemysław> types/methods/fields at point, even if they are in
Przemysław> external libraries (sources usually can be downloaded
Przemysław> from Maven repo).
Jumping between classes works pretty well for me. The rest of it, yes,
it needs some improvement.
Przemysław> 5. Finding usages of fields, methods, types. I use it
Przemysław> everyday for finding dead code. It's also for
Przemysław> refactoring tools.
Yep, that would be awesome. As far as I know semantic is totally capable
of doing this, though a fork might choose to do it totally differently.
Przemysław> 6. Debugger with GUI. There was such project. Maybe it
Przemysław> could be integrated with JDEE sometime.
The jdb integration actually does work (I've made edits to the code to
fix warnings, and tested it recently) but it is very hard to set up
for a "real" project. What debugger do people actually use?
Przemysław> 7. Jump to compilation errors During editing and form
Przemysław> build tool window.
This works extremely well for Ant.
I personally add this to get Maven 2 "support"
(require 'compile)
(add-to-list 'compilation-error-regexp-alist 'maven)
(add-to-list 'compilation-error-regexp-alist-alist
'(maven "\\(^/.+?\\):\\[\\([0-9]+\\),\\([0-9]+\\)\\].*"
1 2 3))
and use M-x compile and it gets the job done for me. I wish I had more,
and I'm personally going to put something together in the weeks to
come.
Przemysław> 8. Execution of selected tests (especially currently
Przemysław> edited one) It's just TDD routine.
Przemysław> 9. The most common refactorings Rename
Przemysław> field/method/class. Extract method. Move class (for
Przemysław> example static nested class to it's own file). 10. Easy
Przemysław> way to write extensions for JDEE.
Przemysław> 11. Configurable indentation.
This one already exists in JDEE but is poorly documented/designed (if
you think the underlying cc-mode indentation is good enough).
Przemysław> 12. Facets/extensions for common technologies (Spring,
Przemysław> JPA/Hibernate): - indicate which classes are Spring
Przemysław> beans - jump to a bean definition - find beans
Przemysław> implementing given interface
All good ideas for people who need them, I agree.
Przemysław> BTW As a developer I can contribute Java, elisp, and
Przemysław> some Clojure if needed.
If you are using JDEE regularly (or even otherwise) I'd be happy to
accept any fixes, or even bug reports with an offer to help test fixes
on platforms I don't have.
I think the biggest issue is generics - and that leads to beanshell. I
suspect that is where the fork comes in....
Cheers!
Shyamal
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
jdee-devel mailing list
jdee-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jdee-devel
