This is purely a hunch, but I've seen sections of the Avalon build that uses ant properties to set things for Jelly to use which could potentially cause this. Because ant properties behave differently to jelly (ie first wins instead of last wins), this can break in certain situations - and changes somewhere in the late betas did just that.
Did it work with different versions of Maven? - Brett > -----Original Message----- > From: Niclas Hedhman [mailto:[EMAIL PROTECTED] > Sent: Tuesday, 30 March 2004 3:36 PM > To: [EMAIL PROTECTED] > Subject: [multiproject] Strange... > > > > Hi, > > I am getting the following strange exception when running > multiproject:install > on RC2 > > BUILD FAILED > File...... > file:/home/niclas/.maven/plugins/maven-multiproject-plugin-1.2 /plugin.jelly Element... maven:reactor Line...... 202 Column.... 9 Unable to obtain goal [multiproject:install-callback] -- file:/home/niclas/.maven/plugins/maven-jar-plugin-1.4/plugin.jelly:32:40: <ant:jar> /home/niclas/dev/opensource/avalon-excalibur/file:/home/niclas/dev/opensourc e/avalon-excalibur/compatibility not found. Total time: 28 seconds Finished at: Tue Mar 30 13:29:05 MYT 2004 'compatibility' is the subproject name. Somehow, the "/home/niclas/dev/opensource/avalon-excalibur/" top-level directory is added in front of the "file:/home/niclas/dev/opensource/avalon-excalibur/compatibility" sub-project dir. Any clues what I have missed? Niclas -- +---------//-------------------+ | http://www.bali.ac | | http://niclas.hedhman.org | +------//----------------------+ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
