[stellation-res] CLI installation and STELLATION_HOME?

[Ringo De Smet <ridesmet@xxxxxxxxxxxxxxxxxxxxx>]

Guys,

You all know that I have been away from Stellation work for quite a while.
As a result, I used the documentation on the Stellation website to build and
install the CLI version of Stellation. Although everything is explained
somewhere on the website, I couldn't find a good coherence in the docs. As a
result, I have bits and pieces of my Stellation setup scattered in three
different places:
1) C:\Documents and Settings\opt\stellation-lib
2) my source folder
3) C:\Software\Stellation

As a user, I first of all want to install the software where *I* like it. So
I created "C:\Software\Stellation" and let my STELLATION_HOME point to that
folder. Then, I was too lazy to read all the little details on all the
different pages to get the system installed. I ran "ant -f build-core.xml"
in my core source folder and it barfed on not finding the cli code.
That's my first question: shouldn't the CLI build system not reside in the
cli CVS module and invoke the build of the core instead of vice versa?

If you try to build Maven (http://jakarta.apache.org/turbine/maven) from
source, they try to limit the number of prerequisites before being able to
use Maven:

- you need a JDK (>= 1.3)
- you need a Ant installed and configures (>= 1.4)
- you checkout the Maven sources from their CVS
- you define MAVEN_HOME in your environment variables.
- you invoke "ant -f build-bootstrap.xml"

When the CVS sources are OK, you will end up with a working Maven
distribution in <MAVEN_HOME>.

I think we should do the same: let the user define STELLATION_HOME, check
out the sources and do a "ant -f build-cli.xml" from within the cli module.
If the cli module can't find the core module, the cli module will do a
checkout (long live the cvs task in Ant) and invoke the build of the core.
It will also retrieve the dependent libraries if not available.

Comments?

Ringo