W dniu 04.05.2015 o 16:44, Paul Landes pisze: [...] > - Move to Github I've moved JDEE to Github (https://github.com/pwojnowski/jdee) and did a few updates - removed some warnings and updated to Emacs 25.1, but wouldn't use it now. :-)
The first thing on my todo list is to add automated testing (based on standart ERT) for elisp code. It's absolutely essential for any project that don't want to be dead in long term. Having automated test can safely refactor code - remove duplicated and dead code, add new things, and just do any modifications. It's a (good) standard in Java word and I don't see any reason it shouldn't be in elisp too. Another thing is importing projects configured with different build tools (e.g. Maven, Gradle, etc.). Such facility would just call a build tool to get dependencies (source, test, runtime) and construct JDEE configuration. Another (simple) todo is to ease configuring list of available JDKs. E.g. check JAVA_HOME, common paths (/usr/lib/jvm, c:/program files/java), etc. It simple, but ease start for someone who wants to start using JDEE. IMHO it would be best to join forces with malabar-mode and create one good Java support in Emacs instead of duplicating efforts. > In the past, discussion like this has lead to more discussion but no action. > Maybe something will change. "The only time you run out of chances is when you stop taking them" Cheers, Przemysław ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ jdee-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jdee-users
