One of my clients has started showing interest in IDEA. They have an
They need to have projects generated from a dependency list outside of
the IDEA IDE. This should produce an IDEA project that can work on the
source in place, build jars like the outside ANT script, and debug
across projects without pain.
They have roughly a hundred interlinked projects. All of them are built
with ANT. Each ANT project is checked out from cvs and compiled to a
jar, which is then used by projects that depend on it. We track and
enforce these dependencies based an a master project list that shows
what is checked out from where, and what depends on what.
A section might look like:
To make this all work, we generate the ANT build file via an XSLT
transform from a source list of projects.
This all works now, and they want to keep using the project list as the
repository of dependency information. They would become very unhappy if
they had to hand tweak an IDEA project when the dep list changes.
I would be the one writing a new .xsl file to generate IDEA project
files, so that a user who wanted to work on userthingie would just check
out the project list and source, and run the transform. Without them
having to do anything else, the built IDEA project would be able to
debug into dependent projects, build appropriate jars, and the like.
Is this feasible? (In other words, is the project format something that
can be generated, like XML or plain text, without mystery keys.)