Right. Copypaste of the plugin doesn't work because Maven is declarative.
One instance of exec-maven-plugin with multiple s, each
having its own ID (since the default is to collide) and its own set of
arguments, appears to be what's intended.
Unfortunately only the first seems to be running.
(To clarify: Reason I'm asking is that the example of exec:java puts all
the parameters in rather than in , and I'm
not clear on whether I can have for multiple runs, or
move the arguments into the , or something else to avoid
repeating quite so much boilerplate.)
On 11/6/2023 7:14 PM, Josep
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
To: users@maven.apache.org
Subject: Re: Multi-module build, emulating Ant build...
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 sol
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
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-plugi
