Jeremy Volkman schrieb: > > As soon as it's back building, I'll need to fix the bootstrapper > > API issue and revert my experiment with using JBoss serialisation > > for the package cache (tried to work around the Drools bug with > > serialisation) and it's back alive. > > > > Should all be done by next week. > > Great -- looking forward to it. In the meantime I'll just play > around with some of the components involved.
Done, it *should* build from scratch right now and when it's built, it *should* run. First, the optional steps: - checkout HiveApp and run mvn install: https://scm.ops4j.org/repos/ops4j/laboratory/users/raffael/hiveapp/trunk/hiveapp - checkout HiveApp-Maven and run mvn install: https://scm.ops4j.org/repos/ops4j/laboratory/users/raffael/hiveapp/trunk/hiveapp-maven Both projects are deployed to http://maven.raffael.ch and the repository is declared in the POMs, so this step is optional. Now for Loom: - Check out https://scm.ops4j.org/repos/ops4j/laboratory/users/raffael/Loom/trunk - Run mvn package assembly:directory You've now got a runnable distribution in target/loom-1.0-SNAPSHOT-binary.dir/loom-1.0-SNAPSHOT. Next cd to test-project, optionally run rm -r target, then: ../target/loom-1.0-SNAPSHOT-binary.dir/loom-1.0-SNAPSHOT/bin/loom (compile only) ../target/loom-1.0-SNAPSHOT-binary.dir/loom-1.0-SNAPSHOT/bin/loom test (compile only, compile tests, "run" tests) Loom in the IDE: Run configuration: - Classpath: See boot/pom.xml - Main Class: ch.raffael.loom.boot.Loom - System properties: -Dloom.home=/your/project/dirctory (this may actually be nonsense, if running from within the IDE) -Dcom.sun.management.jmxremote (optional) - Working Directory: /path/to/test-project - Loom arguments: -V /path/to/Loom/trunk/plugins This causes Loom to use the mount files instead of expecting a certain directory structure. Like that, you can run it directly from within the IDE, without having to run any Ant tasks or something (you'll have to tell your IDE to compile to target/classes for each project -- or change plugins/mount-common.properties to whereever your IDE compiles to) Use whatever method you like to synchronise the classpaths with the POMs (I'm using Maven Reloaded on IDEA for that). Run mvn appmodule:mountfile to create the mount files that mount the M2 dependencies into the VFS of each module. => Right now, you can simply run Loom from within the IDE. If anything goes wrong with building from scratch, on Windows or whatever, feel free to contact me (Email & Jabber: [EMAIL PROTECTED], or #ops4j). Note that due to a bug in Drools, the package cache is partially broken starting with JDK 1.5.0_09 and completely broken starting with 1.6.0. Cheers, Raffi -- The difference between theory and practice is that in theory, there is no difference, but in practice, there is. [EMAIL PROTECTED] · Jabber: [EMAIL PROTECTED] PGP Key 0x5FFDB5DB5D1FF5F4 · http://keyserver.pgp.com _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
