Jesper Holmberg <[EMAIL PROTECTED]> writes:
> I feel that I am not using all the features of JDEE to the maximum. More
> specifically I seem to have problems setting up my environment so that 1)
> JDEE finds everything it needs to do it's magic stuff and 2) I don't have to
> write a lot of project details when I start a new project. I thus wonder if
> people could share some of their tips how they go about setting up a new
> project.
>
> Here is what I do so far:
>
> I always start a new project with this basic file structure:
>
> .
> |
> - build.xml
> - lib
> - src
> |
> - project
> |
> - prj.el
> - MainClass.java
>
>
> I use ant to bild my projects. Now, the prj.el typically contains the
> following:
>
> (jde-project-file-version "1.0")
> (jde-set-variables
> '(jde-project-name "project")
> '(jde-ant-enable-find t)
> '(jde-global-classpath (quote ("~/src/fasade/project/lib/Library1.jar")
> ("~/src/fasade/project/lib/Library2.jar")))
> '(jde-run-working-directory "~/src/fasade/project/")
> '(jde-build-function (quote (jde-ant-build)))
> '(jde-sourcepath (quote ("~/src/fasade/project/src/")))
> '(jde-run-application-class "project.MainClass")
> '(jde-ant-working-directory "~/src/fasade/project/"))
>
>
> My questions:
>
> 1. Is it possible to set some sort of variable so that I don't have to write
> "~/src/fasade/project" everywhere? I can't set this as an environment
> variable, since it is different for every project.
Not sure about this.
>
> 2. Ant picks up any jar file put in the lib directory and adds it to
> the classpath through lib/**/*.jar. Is there anything similar which can be
> set for JDEE so that I don't have to explicitly name every jar-file I wan't
> to include?
jde-global-classpath will pick up any jar/zip file in a directory set up in
jde-lib-directory-names if jde-expand-classpath-p is enabled.
>
> 3. Is the placing of the prj.el down in the src-tree the correct one, or
> should I rather put it in the project root?
I usually keep it at the top of the project. In my case am working with similar
branches of the same tree, so I just copy the prj around. Another advantage is
that relative path works much better.
i.e set the global classpath to ./lib
Javier
>
>
> TIA,
>
> Jesper
>
--
