Agree. It is a hard to integrate with Maven but NOT that hard. I am the author of dita-maven-plugin at codehaus, I am able to automate my entire Dita build process if all artifact are at maven repository.
dita-maven-plugin is a wrapper around ditaoi ant build so I need full ANT packaging , ditaot minimal package, and jar dependencies like saxon, xerces, fop, etc. dita-maven-plugin does not achieve complete full automation if ANT full package and ditaot package at maven central. However, with ditac, i dont need full ANT to build my dita. The external scripts are also small ( compare to ditaot ) where they can just be zipped together into one artifact. Also the ditac ant build is very small and simple So if ditac source tree can be available at GITHub or some public SCM repository like codehaus/googlecode, I can help to push ditac to maven central easily. Now ditac is the truely alternative to ditaot and in my opinion, it has a big advantage over ditaot due to its simplicity On Thu, Feb 23, 2012 at 6:09 AM, Darren Carlton <[email protected]> wrote: >> We suspect software components which rely so much on large external >> scripts to be quite hard to integrate with maven. >> > FYI: > We use maven for our build because the larger product build, of which we are > a part, uses maven. We keep the ditac JARs in our local maven repository and > the stylesheets and DTDs, which we've customized, on the local file system. > We use the maven ant plugin to run our build. Not sure if this really is the > best way, but it works for us. -- XMLmind DITA Converter Support List [email protected] http://www.xmlmind.com/mailman/listinfo/ditac-support
