Re: [jdee-devel] [jdee-users] Call to Fork or simply for JDEE TODO items
Brought to you by:
paullandes
From: <phi...@ne...> - 2013-05-09 11:33:04
|
Paul Landes <la...@ma...> writes: > At some point you have to download jars (including ant plugin etc) to satisfy > dependencies regardless of ant or maven. Ant doesn't do this > automatically--instead you have to hunt them down and spend a lot of effort in > some cases getting all the libraries versions to play nice. Maven _does_ do > this automatically. And Maven *does* have an offline mode. So, you need to run it once online and then away you go. If you really want to be evil, you can run it once, then tar the .m2 directory and move it around. I think taking a step back here is useful though. What is *necessary* to get things to work is to have Emacs start a Java server which can do stuff, like slime, nrepl, ensieme and so on. There is no reason at all why Emacs needs maven for this. As a secondary point, however, for JDEE to do the right thing, the server needs to be launched knowing the details of the project (for example, having the right classpath and dependencies). This last bit cannot be done generically with ant files because there is not enough information. My feeling is that JDEE should start the server, but not configure it. If maven is being used, then this configuration will be automatic. If ant is being used, it wont. Phil |