Re: Fwd: [GUMP@vmgump]: Project turbine-core (in module turbine-core) failed

Stefan Bodewig <[email protected]>
Newsgroups gmane.comp.java.ofbiz.devel,gmane.comp.apache.commons.general,gmane.comp.jakarta.turbine.torque.devel
Message-ID <874o6ifwex.fsf__13888.7856541716$1301630818$gmane$org@v35516.1blu.de>
On 2011-03-31, Thomas Vandahl wrote:

> CCed to torque-dev for Thomas Fox to know.

> On 31.03.11 16:32, Stefan Bodewig wrote:
>> Gump will hand out the latest Torque jars, i.e.
>> torque-runtime-4.0-alpha1-SNAPSHOT.jar,
>> torque-generator-4.0-alpha1-SNAPSHOT.jar and
>> torque-templates-4.0-alpha1-SNAPSHOT.jar when asked for Torque.  Does
>> the plugin work with these versions?  Which of the jars contains

>>> org.apache.torque.task.TorqueDataModelTask

> It used to be in the Torque generator jar but the Torque generator has
> been rewritten from the ground up by Thomas Fox and probably the plugin
> doesn't know about that.

> Anyhow, Turbine needs the Torque plugin/generator/templates/runtime
> Version 3.3. The current version is not backwards compatible.

That's what I thought.

> What do I have to do to achieve this?

Burn a few goats.

OK, the way Gump works it means Turbine must be built before Torque, so
we must make torque-generator depend on turbine-core (and obviously
remove the torque dependencies from turbine-core).  We'll also need to
check whether any of Turbine's dependencies depend on Torque themselves.

I'll take care of this.

Secondly this means Torque 3.x will be downloaded from Maven central and
put into the local repository.  Given that Torque4 seems to be known to
be incompatible to 3.x (I assume this is intentional) this may be a good
thing so I'd live with it (the alternative would be to use a separate
local repository).

Stefan
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.