Community
Participate
Working Groups
Here is the patch for Windows. It is a fairly big one as it includes fixes for a few Windows and Firebird problems as well as extensive modifications to the script files to support Windows and Firebird. Included with the ant scripts are two model property files that are intended to be copied to a user's home directory and then edited for local preferences. Also note that the default installation location for Windows will be \Program Files\Stellation with the rest of the install tree the same as Linux.
Created attachment 4235 [details] Zip of all patch files You will need to filter out .classpath and .project in core.patch. I was unable to convince Eclipse to ignore them.
I've checked this, and encountered a couple of problems. There are a few patch glitches, which look like tab-related issues. They're no big deal. But the patch build-core.xml in the core project doesn't match up at all, and can't be applied. So it's a no-go, until we can figure out what's wrong. I'd suggest checking if you're up to date with the repository - the kinds of other glitches that I saw look like the kinds of things that could happen if you missed one checkin, and there was a recent checkin that included a bunch of build-file changes.
Created attachment 4566 [details] The complete build-core.xml file This should allow you to moveahead.
The work on this item has been completed and checked in with tag jfg-35267.
Created attachment 4771 [details] Ant build scripts, test scripts and related files for Windows and Linux This zip contains a set of scripts and associated files which have been tested on both Win2K and Linux (RH7.3) systems, in both local-server and remote-server test modes. Zip contents include: - build-core.xml, stellation.build.properties used for building and installing Stellation - test/build.xml, test/stellation.test.properties used for testing the installation - test/runserver.bat, test/runserver.sh used for launching a Stellation server for remote-mode testing Build and Test Script Changes - changed build-core.xml (build script) and test/build.xml (test script) to create stellation.build.properties and stellation.test.properties if not found, using default settings - changed build.xml to fail with appropriate message if stellation.build.properties does not contain all settings required) (note: this failure occurs by design when the default stellation.test.properties file is created). - added force-init target to build.xml. This is needed to properly set up a remote test using a localhost server. The remote test procedure is: a) stop server (if running) b) if necessary, modify stellation.test.properties to select remote mode or other settings c) in org.eclipse.stellation.core/test, run "ant force-init" to create and initialize a clean test db d) start server (e.g. via runserver.bat or runserver.sh) e) in a separate console window, run the remote tests: in org.eclipse.stellation.core/test, run "ant" This is **different** (and more convenient) than the previous test procedure. Formerly, it was necessary to: - manually delete the old test db (e.g. 'dropdb tsvctest' ), - create an empty test db (e.g. 'createdb tsvctest') - initialize the db for use by Stellation (e.g. 'tsvcadmin .....'). Now, "ant force-init" does the whole job. Script Additions - added test/runserver.sh and test/runserver.bat scripts to conveniently launch a Stellation server for remote-mode testing. These scripts include hard-coded database pathnames, and require customization before use. They also enable verbose debug output and logging to a file. Other Notes "ant -verbose some >test.log 2>&1" is very useful when debugging the test script. This command-line redirects all output to test.log, and runs a single test rather than the full set of 14. The '+' separator _must_ be used within the repository location specifier. The previous separator, ':', is now treated as a legal pathname character. Windows pathnames in property and batch files should use '/', not '\' . Use of '\' causes weird problems (e.g. damaged pathnames) because it is sometimes interpreted as an escape character. Under Windows, "installed" files are put in possibly-surprising locations. - The test and build property files are copied into ${user.home}/stellation. On my Win2K system, this resolves to "C:\Documents and Settings\jwright\stellation" - The scripts and library files are copied to locations under ${inst.path}. On my Win2K system, this resolves to "C:\Program Files\Stellation" Also - a number of 3rd-party libraries are needed for the installation. The build-core.xml install target expects to find these libraries in ${build.class.lib}, which defaults to ${user.home}/stellation/lib. On my Win2K system, this resolves to "C:\Documents and Settings\jwright\stellation\lib" . All of these default locations may be changed by appropriate use of the stellation.build.properties and stellation.test.properties files.
