Unfortunately this is pretty much incompatible with Maven. However, it is also a huge pain for a project to circumvent the project dependencies in Maven, which gump now has control of, so it should be ok philosophically?
Anyone putting JARs in CVS and adding them to the build classpaths in their maven.xml's can get slapped around by anyone who notices :) Cheers, Brett > -----Original Message----- > From: Nick Chalko [mailto:[EMAIL PROTECTED] > Sent: Thursday, 12 February 2004 10:05 AM > To: Gump code and data > Subject: Re: Building using Maven ... > > > build.sysclasspath=only > > Is a key feature of gump. Gump does not trust any project to > set it's own classpath. it always completely handles the classpath. > > > > Adam R. B. Jack wrote: > > >>Quite simple when I looked at the build.properites - > >>build.sysclasspath > >> > >> > >only > > > > > >>is the problem here. What was the reason for including this > for Maven? > >>Anyway, it works without it. > >> > >> > > > >I was just replying that this might be a factor. Reason? Habit. I'll > >take it out & try. > > > >[What is odd is I think I still pass the CLASSPATH in the env, so > >wonder why that didn't work. Does ant (or whatever is inside > Maven) not > >transfer environments?] > > > >regards, > > > >Adam > > > > > >--------------------------------------------------------------------- > >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] >
