W dniu 19.08.2015 o 15:43, Phillip Lord pisze: >> Now everything has to be downloaded and build every time anything changes - >> elisp or java. > No. You put a "version required" into the Elisp, then check the Java at > start up. You update the Java only when the elisp demands it. Hm... I think I did use wrong expression. I meant that currently there's no such functionality, so use has to rebuild everything every time. If/when we add "version required" then we'll let know when Java rebuild is needed. We can add that into our backlog and implement that.
>> As of now elisp side changes way faster that java, so the elisp side >> is more important to build and install automatically, which cask >> branch does. Having to manually build and install a JAR once is not a >> big problem. > > I guess, but it would be unfortunate if the MELPA install just crashed. > At least we need something which cleanly catches the error and reports > something sensible. Better would be to cleanly "optionalise" all the JVM > dependent technology, but that would be probably be more effort than > it's worth. In won't crash on install - I've checked that. When someone tries to use Beanshell functionality then it checks jde-server-dir and tells user to set it. Of course, later we can (and even should) improve that to be more user friendly. But this is another story. >> This way or another lets do one thing at a time. >> Move to cask and elpa allows us to release frequently and use libraries from >> package manager. Moreover it makes it easier for users to install and update >> the package. So IMHO we should do that despite manual installation of JARs (I >> can make it only one JAR). > > I think that you are probably right. I'll wait until Friday morning (UTC). If nobody argues against I'll merge the cask branch into master and transfer pwojnowski/jdee-server to jdee-emacs/jdee-server. Further we can extend both parts in different directions, but this will separate elisp part from Java and allows to add JDEE to an elpa repository. Then we can turn all recently discussed issues into GH issues and improve based on that. ------------------------------------------------------------------------------ _______________________________________________ jdee-devel mailing list jdee-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jdee-devel
