Hi Wendell, no, actually this is even bad practice. You should always explicitly set the required version in your pomfile. Otherwise, your application always uses the latest version and isn't realiably testable. The following should fetch BaseX 7.9, the latest stable release: <dependency> <groupId>org.basex</groupId> <artifactId>basex-api</artifactId> <version>7.9</version> </dependency> For Saxon, if you have the jar file in your lib you should be good to go (are you sure however that you included it via maven). Should be somethin like that as dependency: <dependency> <groupId>net.sf.saxon</groupId> <artifactId>Saxon-HE</artifactId> <version>SAXON-VERSION-YOU-LIKE</version> </dependency> Cheers, Dirk On 01/18/2015 10:29 PM, Wendell Piez wrote:
BaseX friends,
If I run BaseX from Maven, do I always get to use the latest BaseX?
Do I have to do anything special to set up BaseX in Maven to use SaxonHE instead of Xalan for xslt:transform()? (I have Saxon9he.jar in my BaseX lib.)
Thanks! Wendell
-- Dirk Kirsten, BaseX GmbH, http://basexgmbh.de |-- Firmensitz: Blarerstrasse 56, 78462 Konstanz |-- Registergericht Freiburg, HRB: 708285, Geschäftsführer: | Dr. Christian Grün, Dr. Alexander Holupirek, Michael Seiferle `-- Phone: 0049 7531 28 28 676, Fax: 0049 7531 20 05 22