[I assigned this "blocker" priority because the current HEAD can't build projects that need the torque plugin like the Turbine 2.3 code base. So using this maven stops work on these projects ]
Due to some change in jelly, maven or somewhere else between the
1.0-rc2 and the current 1.0 HEAD version (which identifies itself as
1.0-rc3-dev), the Torque Plugin, which relies on using the Ant Task
interface no longer works.
The reason for this is in the JellyPropsHandler class which interfaces
the JellyContext onto ant Properties. For this, it calls toString() on
values in the JellyContext.
Up to some points, expression elements in this context returned its
evaluated value. At some point this seem to have changed and the
elements now return
so code that uses these elements starts to use really scary stuff.
I wasn't able to pinpoint the exact location where the problem crept
in, because I simply didn't want to try to understand the "inner
workings" of the maven code. It might have to do with the changes in
the MavenExpressionFactory; it could simply be because a newer
jelly version is used.