Re: [jdee] jde-help-class: (void-function sort-helper) (#10)

flesner <notifications <at> github.com> writes:
> it appears that checkin a3f95b051e430c27f00dc17e3c995cbdf71807bb broke
> the javadoc helper classes.
Sorry, that was me. I didn't test very thoroughly (I'll get around to
adding more tests soon).
I can reproduce the problem; on a source line:
Context context;
with point on Context, M-x java-help-class hits this error.
It appears the problem is this line in jde-open-source.el
jde-choose-class:
(setq classes (sort classes 'sort-helper))
Apparently trying to reference (as opposed to call) a symbol that is
defined with cl-flet doesn't work.
I changed it use plain 'let', with 'lambda'. Now it works.
Fixed in a7f2d569b6a005c9ad227d5f70629558f32246c, merged and pushed in
0222cd7744499aeb6f29cb7c628f477d4a8c0b4
> my current stack trace:
>
> Debugger entered--Lisp error: (void-function sort-helper)

I recall that there used to be several steps to install JDE, such as getting the right version of CEDET. That isn't any place obvious at the git site.

Are the instructions somewhere, along with something I can install without building?

I did download the source and try building that, but there are errors in it. jee-complete-pair has unbalanced parentheses, and jee-import-find-all-and-import defines vfn in a way that it cannot be called later.

Some stories from a user

Hello!
I've been enjoying the recent flurry of JDEE activity. Thanks everyone, keep it up! I've tried JDEE now and
again over the years, because I love emacs (though I'm still a novice).
But, I always go back to Eclipse. Sometimes I'll open a .java file in Emacs in fundamental-mode to do some
text manipulations. Eclipse doesn't have c-x (!
I think I see conversation participants not grokking each other on the subject of Maven. Maybe I can help.
Maven is this huge thing in the corporate slave/java dev's life. It's not *really* a build tool. Neither is
emacs isn't an email client! ...It's a poor analogy, but stick with me... (Unless you find the following
very obvious--in that case, it's for the other reader!)
Maven is a dependency manager. Here's how it works:
I'm hacking on CoolClass.java and I want it to tokenize some strings. My DWIM Java hacking environment
(Eclipse) has some shortcut keys... c-SPC does completion on a class name. So:
foo = new StrTo[c-SPC]
should expand to:
foo = new StrTokenizer(
(at least.) But, I don't have the jar for the library that contains that utility class on my classpath!
Enter Maven. I use a web search engine (or built-in Eclipse feature, but it's not very good) to find this: http://search.maven.org/#artifactdetails|org.apache.commons|commons-lang3|3.4|jar
Then, I add this to my project's (existing) pom.xml:
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-lang3</artifactId>
<version>3.4</version>
</dependency>
As soon as I hit save, I can go back to CoolClass.java and hit c-SPC again. It will work.
Maven didn't just download the jar I specified and save it somewhere in the project. It first consulted the
user-wide cache of previously downloaded jars. Maven also checked if the library I requested depends on
other libraries and downloaded them, too (recursively).
Not only that, but my dev environment can now magically pull up the JavaDocs for the new class. If I start
debugging and step into that class, Maven will download the source code for me, too. (Actually, I guess
Eclipse invoked mvn several times to perform each of those actions individually.)
Maven is also a community. There is such a thing as doing things "the maven way". (Note: I'm a novice! If you
are too, just have a look at the 20kb POM I linked above, maybe even before the Maven homepage.)
To be clear: I'm not saying JDEE must do things the maven way, but I am saying that acknowledging that it
exists, and that an Eclipse way exists, will do a lot to help JDEE grow, and help me use it.
Powerful refactoring is more important, but I have no fear that Emacs will excel at that. I leave it in your
capable hands.
Well, this email is too long already. But, I hope it has been helpful.
Cheers,
--Dave
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/

branch for emacs master work

I'd like to create a branch for work on upgrading to emacs master (aka
emacs 25).
Is the git branch name "emacs-master" acceptable?
Then when emacs 25 is released, the emacs-master branch is merged to
master, and emacs-master starts working towards emacs 26.
--
--
-- Stephe
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/

Automated testing

Hello everybody,
I've added Ant task "test-lisp" that runs tests from "test" directory.
At this moment there's only one test, but it works - test is executed
from Ant and the test has dependency on build/lisp/jde-util.el.
The only thing that has left is to extend this task to go through all
test/*test.el files and execute them, not just the hardcoded one.
Cheers,
Przemysław
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
jdee-devel mailing list
jdee-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jdee-devel

Next Gen JDEE

Paul Landes <landes <at> mailc.net>
2015-07-14 13:57:24 GMT

I'd like to bring up the topic of a major refactoring. I don't think I'm in the minority in the mode of thinking
that JDEE needs a major refactoring given:
- Girth of the project: it's a lot to maintain and various plugins might not be used any more
- Inertia: without a lot of activity there's less interest
- Popularity of Java: Java is much less popular, and thus, used. That said, I think for us who use it less we
still need it much like a C programmer might still at times need to view or modify bits of assembly.
Again, my earlier plans were to create a brand new project and port over pieces from JDEE. Starting new I
think is necessary to start the ball rolling where as a major refactoring of the existing code base would be
an up hill battle against the mentioned inertia of a large project.
To reiterate from a previous thread, some top level ideas:
- Replace beanshell with clojure
- Replace semantic with some Java based parser (maybe compiler like ASM)--however all fly compilation and
syntax correction etc happens in Java. This includes more advanced high lighting.
- Entire project becomes an Emacs plugin
- Move to a plugin approach so each add on is a separately maintained Emacs plugin. If someone wants to
resurrect jde-debug from JDEE into the new version, then that person creates a new Emacs plugin that fits
in some next gen JDEE plugin architecture. This gets rid of some bloat ini the core next gen JDEE.
Question in order of importance:
- Who has the time and initiative to help out (I can't do it all myself with current time constraints)
- Should the project have a new name or carry the same name? My feeling was start a brand new project for the
purpose of name space and maybe create more "buzz" as a "new" Emacs java development library.
Given all of this, I'd like to hear others opinions how to proceed with JDEE--especially from the previous
contributors of JDEE, which I've seen more of lately.
Regards,
Paul
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/

Documentation in texi

Hi.
Sometime ago I've ported all docs (without images) from HTML pages to
Texinfo format. Both User's and Dev's Guides are in one file but
different sections.
The file is in the repository: doc/jdee.texi
It's not beautiful, but complete and works better than applets.
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/

Supported Emacs versions

Hello everybody,
What version(s) of Emacs should be supported?
Are we plan to still support Emacs lower than 25?
IMHO there's no point in maintaining older versions. If someone wants to
use JDEE with older Emacs, then releases 2.4.x are available.
Cheers,
Przemysław
------------------------------------------------------------------------------
Don't Limit Your Business. Reach for the Cloud.
GigeNET's Cloud Solutions provide you with the tools and support that
you need to offload your IT needs and focus on growing your business.
Configured For All Businesses. Start Your Cloud Today.
https://www.gigenetcloud.com/
_______________________________________________
jdee-devel mailing list
jdee-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jdee-devel