Have you tried specifying the specific Jexl version you want in the plugin configuration? Too lazy to insert the proper artifactIds and groupIds, but you should get the idea...
<build> <plugins> <plugin> maven2-xdoclet2-plugin <dependencies> <dependency> jexl <version>1.0</version> </dependency> </dependencies> </plugin> </plugins> </build> This might work? If not, try <version>[1.0]</version> instead. Wayne On 4/19/06, Brian Wainwright <[EMAIL PROTECTED]> wrote: > > Hi, > > I have a problem where I am using the XDoclet2 plugin to generate Hibernate > mappings for my DAOs, which works fine for all but one mapping. An (invalid) > stray element is being written to the mapping file because of two (optional) > attributes are missing from the Hibernate/Xdoclet tag in the classfile. > > I've tracked the problem down to be a problem with Jexl (used to > parse/execute Xdoclet's Jelly script when generating the mappings), where it > seems it's empty() function doesn't work in version "1.0-beta-2", but does in > "1.0". The problem is that "maven2-xdoclet2-plugin" is pulled in from the > Codehaus repository as a snapshot version, which in turn pulls in a snapshot > version of XDoclet2, which itself uses the broken (1.0-beta-2) version of > Jexl. > > Is there a simple way to restrict the version of the Jexl dependency? The > only way I can think at the moment, is to have custom versions of the > dependencies on our own internal repository and hack the pom's to force the > use of specific versions all along the dependency chain? > > Thanks for your help! > > Brian Wainwright > Developer > Burns E-Commerce > Mansion House, Manchester Road, Altrincham, Cheshire, WA14 4RJ, UK > http://www.burnsecs.com > mailto:[EMAIL PROTECTED] > > > >
