(To clarify: Reason I'm asking is that the example of exec:java puts all
the parameters in <configuration/> rather than in <execution>, and I'm
not clear on whether I can have <configurations/> for multiple runs, or
move the arguments into the <execution/>, or something else to avoid
repeating quite so much boilerplate.)
On 11/6/2023 7:14 PM, Joseph Kessselman wrote:
Turns out Stylebook does have a front-end driver that I don't have
source for, so I'm just invoking it via exec:java for now. I'll clean up
later. At least it gets rid of the platform-specific script and puts the
pom in charge of everything.
Quick question re exec-maven-plugin: Is it possible for one instance of
the plugin to run multiple executions, or should I just rely on copypasta?
On 11/4/2023 7:53 PM, Joseph Kessselman wrote:
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
