One more thing... Scarab (scarab.tigris.org) uses an older branched version of jakarta-turbine-fulcrum. This produced a single large jar called fulcrum.jar. However, Fulcrum head, and the current item to integrate is a series of seperate components. So, I believe this means that we need to create some sort of project dependency, similar to how projects depend on mail.jar.
I don't think there is any real need to build this branched version of Fulcrum as only jakarta-turbine-3 and scarab rely on it. and turbine 3 is a dead end development "spike" and Scarab is moving away from the branched to the CVS HEAD version of fulcrum. Eric > -----Original Message----- > From: Stefan Bodewig [mailto:[EMAIL PROTECTED] > Sent: Tuesday, October 12, 2004 12:40 PM > To: [EMAIL PROTECTED]; Turbine Developers List > Subject: Re: Gump descriptors for Fulcrum components. > > > On Tue, 12 Oct 2004, Eric Pugh <[EMAIL PROTECTED]> wrote: > > > And what does this error mean? I notice in the gump config file > > that there is a dependency on commons-beanutils-core. > > I changed it after the build failure. > > commons-beanutils has been split into *-core and > *-beanutils-collections. For most projects replacing > commons-beanutils with commons-beanutils-core just worked. > > I have no idea what you'd have to do to make it work with Maven. I > don't believe there's been a release of beanutils that would reflect > this change, yet. > > > Does that mean I should be depending on that somehow in my > > project.xml? > > Probably. > > > Or, should I update the dependency in the gump file to > > commons-beanutils from commons-beanutils-core. > > There is no commons-beanutils in Gump anymore. > > 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]
