[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [stellation-res] CVS Directory Structure
|
At 05:14 PM 3/2/2003, Jonathan Gossage wrote:
I think that anything we do for the alpha release should meet the following
objectives.
1. Be reliable.
2, Support both Linux and Windows.
3. Allow easy use of any compiler and JVM. For example, I have had no
success with the Jikes compiler and the IBM JVM under Windows but have had
no problems with the Sun environment.
4. Allow the use of any tested database for both testing and normal use.
I agree with these objectives.
The third and fourth objectives mean the removal of direct dependencies in
build/install and test scripts.
Could you clarify what you mean by direct dependencies?
In the patched build-core.xml file, I added a number of new properties
for various installation-specific paths, to enable command-line overrides.
Motivations:
a) to reconcile some contradictory path usage;
b) to allow easy script adaptation to the local environment (without hacking
the script itself)
The modified test script (stellaton.core/test/build.xml) includes a number of
new properties for similar reasons (the script currently in CVS assumes use
of some 'magic', sparsely documented user names and/or passwords).
I think that we should not worry about
convenience issues until afyer we have achieved reliable installation and
invocation for the core configurations.
Yes. At present, I'm only thinking about something Stellation developers
can use
(not something for end users).
I have now got your patched build-core.xml and will see if I can quickly
build this into something that will meet the above objectives.
Looking forward to seeing it ---
Thanks!
Jim
--------------------------------------------------------------------
Jim Wright, IBM T.J. Watson Research Center
*** The Stellation project: Advanced SCM for Collaboration
*** http://www.eclipse.org/stellation
*** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
jim.wright@xxxxxxx
