Hi Joseph.
Just some thoughts:
-- Stylebook seems to be a DocBook variant or extension. Maybe you
could with little effort change the documentations to conform to
DocBook and then use existing Docbook solutions for Maven.
-- Scripting the build Ant-style by using Groovy or Bsh from
corresponding Maven plugins is another, albeiut ugly, option. So is
using Ant from Maven.
-- You could write a simple Maven plugin encapsulating the minimal
behaviour you need, publish it use it for Xalan.
-- You could convert Stylebook to AsciiDoc and use existing Maven
plugins to generate the documentation. Last year, I started to
convert the DocBook and HTML files from the AspectJ documentation
to AsciiDoc. I did the heavy lifting with Pandoc, batch-converting
the DocBook stuff. Then I manually fixed up stuff like code blocks
and other details to be as clean as I like them to be, which was
tedious, but manageable. Back then, I did not finish my work,
because the last step, changing the Maven docs generation stuff,
has not been done yet, but the files look pretty nice already and
can be directly displayed inline on GitHub, because, well - they
are AsciiDoc now.
HTH. Regards
--
Alexander Kriegisch
https://scrum-master.de
Joseph Kessselman schrieb am 05.11.2023 06:53 (GMT +07:00):
> 1) For backward compatibility with the prior Ant build (and with the
> test framework's assumptions about where compiled code will land), I
> have my maven build creating ./build/ in the top-level directory and
> copying the jarfiles from the individual modules up to that using
> maven-dependency-plugin. It would probably be a good thing to copy the
> modules' *-sources.jar files there too, but I haven't found a syntax
> which will do that without also copying all the dependencies'
> sources.jar files. Any tips?
>
>
> 2) Some of Xalan's older documentation was written in stylebook. I'm
> currently handling that by running a post-build script (.sh or .bat) to
> execute the org.apache.stylebook.StyleBook class several times with
> appropriate arguments. It'd be more elegant to invoke that from the pom,
> of course, for clarity and portability... but I haven't yet gotten the
> exec plugin to Do The Right Thing. The needed command is something like
> (in Linux syntax):
>
>
> java -cp
> stylebook/stylebook-1.0-b3_xalan-2.jar:tools/xalan2jdoc.jar:serializer/target/classes:xalan/target/classes
>
> org.apache.stylebook.StyleBook loaderConfig=sbk:/style/loaderdesign.xml
> targetDirectory=./target/site/design/
> ./stylebook/sources/xalandesign.xml ./stylebook/style
>
>
> ... where of course the */target/classes are the compiled sub-modules
> and could just as easily be the generated jarfiles and referenced as
> maven artifacts (right?).
>
> Might be possible to use the ant-stylebook plugin instead, but that
> seems to be deprecated, not well documented, and have CVEs against it...
> which last probably apply to my local copy too, admittedly.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
