Re: [CEDET-devel] EDE projects for JVM-related languages & build tools
Brought to you by:
zappo
From: Alex O. <al...@gm...> - 2012-10-19 06:46:28
|
Hello Oleg What is a language that you're using? Do it have it's own build tool? My idea is to create a base for java-based project that have some common things, like project file in the root of project, classpath, etc. I plan to commit some Maven-related changes over weekend (although I'm not sure that I'll have much time due surprisingly good weather ;-) or maybe during next week. After Maven support I plan to add support for Clojure's Leiningen, although we don't have parser for Clojure yet... Simon Brown <li...@70...>, c On Thu, Oct 18, 2012 at 2:13 PM, Left Right <ole...@gm...> wrote: > Not sure if my comment belongs here, if not, I'll start a different thread. > > I'm right now reading on extending EDE and the basic concepts. I'm > looking for a tool to provide project support for a language mode I'm > trying to improve. I've tried first eproject from elpa, but I don't > like it for many reasons not really important to mention here. > I would be very interested to see an EDE Java project, because the > language I'm working on has similar concepts in terms of how sources > are arranged. Please, if it is possible to share it, Alex, it would be > perfect! :) > > One particular thing that I'm not feeling content with EDE projects is > the requirement of Project.ede file to reside in each subdirectory of > the project tree. The typical for Java style of arrangement of the > sources is to have deeply nested hierarchies of directories, many of > them would appear empty or be created only because the codestyle guide > says so. I.e. it is typical to have > /src/java/com/enterprise/project/module/components/group/ui/impl/Button.java > kinds of names :| Where most of this path would appear as not > containing anything else but other directory trees. > So, does it sound reasonable to only have one Project.ede file per > actual project? Also, note that project sources aren't necessary under > the same physical directory tree on the file system. In fact, it is > common to reference sources which don't share a common directory root > under the same project. > Perhaps, if I need to elaborate, the tools working with the sources in > these kinds of projects assume this state of events to be typical and > normally don't require sub-directories and files to be provided to > them one by one, instead, they would expect to be given a reference to > a directory tree, which contains the sources. Thus having Project.ede > files in the "intermediate" directories would serve no purpose from > the stand point of compilers / debuggers etc. Another impediment would > be that other IDEs don't save project info in this way and sharing > source code with people not using Emacs would make it problematical to > maintain a consistent project structure. > > Or maybe have I goten a wrong understanding of it? > > Best. > > Oleg > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_sfd2d_oct > _______________________________________________ > Cedet-devel mailing list > Ced...@li... > https://lists.sourceforge.net/lists/listinfo/cedet-devel -- With best wishes, Alex Ott http://alexott.net/ Twitter: alexott_en (English), alexott (Russian) Skype: alex.ott |