>> So my questions at this moment are: >> >> 1. Should building avalon itself build all the subdirs as well ? >> 2. Do you need to ever do an ant build, or is it always a maven build ?
>Maven have had a lot of problems with its 'reactor' (meaning building all in the subdirs as well), so either noone relies on it, or there is explicit invocation in the maven.xml where Stephen has though it is too much hazzle to go into each directory manually. >I don't understand Maven enough, so I added the build.xml (Ant) in avalon root, which just invokes a bunch of maven where required to get Merlin on its feet from a fresh checkout. (However, it probably doesn't work on all platforms). >If you had any luck building from avalon root, then I think it was because you had a Maven fresh enough to work better. It doesn't work for me with -rc1. >Cheers >Niclas So, if I read you correctly, if I do an "ant clean" it should then do a "maven" command in each of the following sub directories ? framework meta util repository logging merlin And the result of such an ant build should be the same as if I execute maven in each sub dir manually ? Also, I'm wondering about a previous commment: If > you don't want to maintain a separate runtime, set it to /dev_sandbox/avalon/merlin/target/merlin I dont have a sub dir in merlin named target. my sub dirs are activation composition facilities kernel platform how do i get the target dir ? (running maven in the merlin dir did not create it) Thanks for the help, Andy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
