Re: docbook + maven
by Steve Ebersole
> Sure. What we do is we package the styles in a zip file using a
> standard maven project and the build-helper-mojo from codehaus. The
> zip file contains not only the CSS, the XSLT parameters but also the
> images linked to the style.
>
> Next, in a "doc" project, we depend on the zip above and we use the
> dependency plugin to inject the data (dependency:unpack) in the
> target/${artifactId} directory where the docb sources are copied.
I am not overly familiar with this dependency plugin, but the overall
approach sounds essentially the same as I described in my "staging"
approach. The concern I had was knowing which dependencies to pull
resources from. I would then guess that this dependency plugin you
mention requires you to explicitly state the coordinate to be unpacked;
essentially doubling the config?
> Now, we have a hard dependency on xmlto for the actual generation. If
> we can use a more elegant solution, I'll be glad to test :)
I am not overly familiar with 'xmlto' other than the fact it exists ;)
>From my understanding, it is an xslt framework, right? I just use SAXON
inline with the plugin using a Transformer built based on the
configuration, project, etc. The only drawback I have seen is the fact
that SAXON eats large amounts of memory.
17 years, 7 months
Re: docbook + maven
by Steve Ebersole
On Tue, 2007-06-05 at 09:18 +0200, Stephane Nicoll wrote:
> I am currently migration our doc on docbook+M2 and I ran in the same
> issues. Is your plugin freely available?
Sure, as of now it is in Hibernate SVN and published to the JBoss Maven repo.
> Regarding styles, we also use them as dependencies and images are
> located alongside the docbook file.
Images alongside the DocBook source is fine for images referenced from
those sources; that makes sense. But I am talking about images packaged
with the styles. Remember, the whole point is to have reusable xslt
bundles.
17 years, 7 months