I think that we should still be building chainsaw as part of the core build. Can't we define the dependency on ORO in the Gump build scripts? It should already be aware of the other optional dependencies.
Maybe the chainsaw build target being executed should be dependent on the ORO jar being available, just like the other dependent build targets in the log4j build. Then the worse that would happen is Gump would not build chainsaw until it defined the ORO dependency. -Mark > -----Original Message----- > From: Paul Smith [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 25, 2003 5:03 PM > To: 'Log4J Developers List' > Cc: '[EMAIL PROTECTED]' > Subject: RE: [Gump] build Failure - caused by changes to chainsaw > > > > I've been wrestling with getting struts to compile under gump and > > hopefully i've fixed it. But I am not sure since log4j > > isn't compiling > > under gump. > > > > The URL I pointed to above has the full detrails. > > Hi Rob, > > This one's my fault. I've modified the Log4j build.xml so the default > target does not require the Chainsaw component to be built. > It was this > area of Log4j that requires ORO. > > I've just done a test by typing "ant" in the jakarta-log4j > module (after a > clean) and it seems to compile fine. Hopefully this will > solve your issue. > > cheers, > > Paul Smith > > --------------------------------------------------------------------- > 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]
