Since THE GREAT OVERHAUL (TM) I have repeatedly failed to build Merlin from a vanilla checkout of the avalon module. Presuming that the old way of building the meta, util, repository and merlin submodules separately is now obsolete I tried a simple 'maven' from the top level avalon directory. This fails with a 'no goal: [avalon:install]'. This raises the question of which maven plugin defines this goal. I had some trouble upgrading maven to rc2 and in the end nuked my whole maven installation so that my old plugins are lost. Scanning through the sources of the various maven plugins to be found under avalon I could not find suitable candidate.
Trying the old way of cd meta maven fails with BUILD FAILED File...... file:/C:/Quelltexte/OBergner/CVSCheckout/ApacheGroup/Avalon/avalon/meta/mave n.xml Element... maven:reactor Line...... 52 Column.... 31 Unable to obtain goal [jar:jar] -- file:/C:/Data/OBergner/Maven/unpacked-plugins/maven-jar-plugin-1.4/plugin.je lly:32:40: <ant:jar> C:\ Quelltexte\OBergner\CVSCheckout\ApacheGroup\Avalon\avalon\meta\buildsystem not found. Total time: 36 seconds Finished at: Tue Apr 20 15:08:13 CEST 2004 which probably indicates that maven erroneously looks for the buildsystem submodule in a directory relative to the current directory instead of relative to the avalon directory. Or maybe the mere attempt to do do what I am trying to do at this point in time is a sure token of hubris? Should I rather wait until the grounds stop shifting? Olaf --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
