Most of these have been fixed in recent maven releases. Which paths were broken?
On Fri, 2 Jul 2004 23:29:33 -0400, Dmitri Plotnikov <[EMAIL PROTECTED]> wrote: > Stefan, > > I am sorry about these paths - I didn't look at the file, just generated it > using Maven, ran it to make sure it still build (which, of course, it did > locally) and checked it in. > > I removed the bad paths manually and committed the fix around 6:30PM, but > GUMP failed anyway at 9PM. Is it possible that there is a manually modified > version of build.xml sitting on the machine running GUMP? > > Thanks, > > - Dmitri > > > > ----- Original Message ----- > From: "Stefan Bodewig" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Friday, July 02, 2004 6:54 AM > Subject: [GUMP] jxpath's build.xml contains "bad" paths > > > Hi, > > > > the build file for jxpath has been regenerated and it now contains > > some awkward looking paths like > > > > <property name="defaulttargetdir" > value="D:\jakarta-commons\jxpath/target"> > > > > instead of target. On a Unix machine Ant will see this as a relative > > path to the basedir lateron leading to build failures (that Gump is > > supposed to report). > > > > Stefan > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- http://www.multitask.com.au/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
